Conrad Ludgate

Conrad Ludgate

@conrad.cafe

Probably writing Rust https://github.com/conradludgate https://conradludgate.com

268 followers108 following394 posts

Conrad Ludgate reposted

Neon now has realtime, built by the team behind Electric. Turn any SQL query into a live query, joins and aggregates included. All inside Postgres, and ready for agents. It’s in public beta and available in all Neon plans. Give it a try and tell us what you think! neon.com/blog/neon-no...

Replacing the HN app on my phone with my weight loss app is probably the most healthy thing I've ever done, both physically and mentally.

Why did I spend my vacation thinking about congestion control and client side load balancing? In other news, I got bitten by a fish in the Mediterranean Sea the other day

I'm mostly using K3 in Codex right now. It's pretty good. It's not cheap but it's comparable with the duopoly. I use it the same way I used Sol or Opus: 1. Sketch out the plan for the feature implementation - several prompts 2. Implement it - one prompt (+skills) 3. Refinement - many prompts

Conrad Ludgate@conrad.cafe

I'm mostly using kimi k3 (open weights) with a bit of Sol (proprietary) on the side at work. Sol is a bit better, but I know Kimi will never stop me when I'm fixing bugs in my service, which Sol is always so happy to do (bugs in my service means security flaws)

During implementation phase, it's committing by itself and writing/running tests. While it's running I'm off doing something else. After refinement I usually use another session with another LLM and I get it to review it. I also make sure I provide my understanding of the feature to compare against

If my understanding is incorrect, then something needs fixing. If a decision was made I should understand why. Currently K3 is very willing to make its own decisions and then think the decision came from a human. I make use of the Codex "approve for me" feature which occasionally flags such issues

Would someone security conscious enough to host an MCP/AI Gateway in their own home then be willing to let the agent run on a VM in the cloud? What if the machine the VM was running on had no direct internal or external Internet access, all access goes through a tunnel service via PrivateLink?

I'm working on an interesting product idea for personal AI that involves lightweight VMs for reproducible LLM evals, but I don't want you to give your API keys to me. If your assistant goes rogue deleting emails you can turn off your gateway and everything stops. All gateway access is logged

I'm thinking that the cost of an rpi running a gateway and the cost of hardware capable of running lots of VMs is quite different. Maybe there's a middle ground there of people who want some better security but don't want to run their own agent harnesses on their hardware. Idk.

I think platforms like github should invest in exposing audit information. An agent should be able to see a log of events that occurred and know whether it was me, another agent, or itself that made some change.

View full thread

The LLM should know that it was an intentional decision and not a mistake it made. I'm working on an experiment that will give each session their own access tokens, but fundamentally it'll require effort from the services to store some identifiers.

Practically I think the information can be private by default and only viewable by the account owner, treating it as a proper audit log rather than leaking more about the setup

I think platforms like github should invest in exposing audit information. An agent should be able to see a log of events that occurred and know whether it was me, another agent, or itself that made some change.

We require all LLM PRs opened in draft mode at first. Very often I'll mark the PR as ready for review but then I'll fix something flagged in review. The LLM will get confused that the PR is no longer a draft and it'll mark it as draft again...

It will be build system agnostic, software packagers can publish nix or bazel or cargo or whatever build system tooling for the package version if they wish. They can even publish patches if they need to.

Despite having brainrotted away using LLMs for 95% of my coding in recent months, I still have breakthrough ideas for code at 2am where I have to wake up and slack myself the idea. It was a good idea. Sol agreed 😝

Do you need anything from a rust testing framework? I end up using pytest a lot which makes me sad, but there's just nothing that comes close in Rust. I'm working on something and I'm interested to see if your usecase is covered by my design

Seems that 16GB VRAM isn't enough for vibe coding just yet. Models trained for tool calls seem to struggle with them when quantized

Conrad Ludgate reposted

It’s actually a great time to care about the craft. I don’t know if people realize this but you can actually write whatever you want into the prompt box. You can use the AI to get the function just right instead of making it generate crap as fast as possible.

Laurie Voss@seldo.com

I have always been the kind of developer who only cared about outcomes. Give me the tool, the framework, the head start. I just want my website. A totally different kind of developer exists who cares about the *craft*. Getting that function just right. Those devs are in pain right now.

Conrad Ludgate reposted

WARNING: Reading this post may cause a little jolt of anxiety every time you cancel a query with CTRL+C in psql. George MacKerron is back with another deep dive into one of Postgres’s strangest corners. neon.com/blog/ctrl-c-...

neon.comCtrl-C in psql gives me the heebie-jeebies - NeonThere are a few different reasons to hit the brakes on a Postgres query. Maybe it’s taking too long to finish. Maybe you realised you forgot to create an index that will make it orders of magnitude qu...

I'm pretty deep in the LLM psychosis right now. It started from ADHD induced burnout for a project I really wanted to work on but I just couldn't get past the mental block. I was able to throw cursor at it and make very solid progress. Now it's also my notes and research assistant.

I haven't written a single line of code in the past two weeks. It's definitely helped me so far. But it's also incredibly addictive. I fire off the prompt, wait, review the plan, wait, build the plan, wait, review the code/test, wait for fixes. Brain will probably explode soon.

I've simultaneously been working less (less active participation from my brain during working hours) while working much more (evenings and weekends). It's easy to fire a quick prompt before you go to eat dinner, then you quickly review and prompt again, then you clean up dinner and prompt again

Conrad Ludgate reposted

The #rustconf '26 Program Committee represents the breadth of the #rustlang ecosystem — from bioinformatics to safety-critical systems, from the UK to Argentina to Nigeria & beyond 🌍 Meet the group of community members that will be reviewing talk submissions: rustfoundation.org/media/announ...

rustfoundation.orgAnnouncing the RustConf 2026 Program Committee - The Rust FoundationThe Rust Foundation is excited to introduce the RustConf 2026 Program Committee - a fantastic group of global community members who will help shape the content and direction of this year’s…
View full thread

Don't get me wrong. Plenty of LLM produced code is slop. And I hate the companies behind the current wave. I'm definitely staying away from depending on them until we get more access to local hosted models. The incestuous nature of current training is also unlikely to end well.

There definitely needs to be an overhaul of the technology and the society, but it's definitely not gonna go away because you make a list of shame. Social media lowered the bar for misinformation on the internet. LLMs lowered the bar for slop on the internet. But neither inherently cause them

Calling any LLM assisted development tainted slopware is definitely a take. I have played around with LLMs in software to help with accessibility (incase I have to stop using a keyboard). It was interesting but I didn't enjoy it, but not because it produced slop. Slop is purely what you make of it

I respect github charging for github actions self-hosted runners because their orchestrater isn't free. However, github actions sucks ass and it's not a compelling product. Not sure what I plan to replace it with. I've been somewhat bullish on CI=build system. Definitely not using nix though.

CI=build system is great because it means you can always run CI locally. And you can often use remote build/cache servers natively. At work we use bazel. It's ok. Maybe I'll invest some time into learning it. Alternatively buck2. But definitely not nix.