Richard Gill

@richardgill.org

Software Engineer / Builder. http://richardgill.org

The best place to show the model the context it’ll need next time is right next to the code. So I’m writing long block comments now. I’m finally ready to work on the Linux kernel...

The software engineering industry tends to change its norms relatively slowly, usually only after doing things the wrong way for a while and feeling the long-term pain. AI has changed nearly everything in just a year. But the norms will take a while to catch up.

The biggest challenge with AI coding is likely to be: building software is still a team sport. Poor use of AI by some team members pushes the real work onto others, who get “splashed” by slop.

I set up a cron job to send me the GitHub notifications I actually want to see. Took 20 minutes. Genuinely baffling that GitHub still hasn’t implemented this.

I’ve been experimenting with using emojis and short acronyms in my `AGENTS.md` file: 🟢 = Babysit the GitHub checks cip = Commit and push 🧵 = Do this in a tmux window Works well

LLMs are currently kind of slow. OpenAI's new gpt-oss 120b is a pretty capable model in the benchmarks (maybe ~1 year behind the state of the art) If you run it on Cerebras you can glimpse the speed improvements that are coming.

Dev tooling often behaves differently if you set CI=true We're going to need AI=true so that dev tools can behave differently when called by an AI agent: - Non-interactive (like CI=true) - Less logging to preserve context - Tell the agent what commands it could run next based on what happened

When you use claude code a lot, it feels obvious that coding with agents on mobile makes sense. Seems likely >20% of 'coding' will happen on mobile within 5 years (presumably from ~0% today!)

If you have a social media app where the DMs are important but you want to stop being exposed to the feed. e.g. LinkedIn or Twitter You can use beeper.com which aggregates chats across multiple platforms. Then block/uninstall the original app.

Was explaining agentic coding to my mum yesterday and found myself saying: "My job used to be typey typey, and now it's chatty chatty" Kind of sums it up nicely.

With Claude Code you can bring it up to speed on a PR by doing this incantation: git fetch origin refs/heads/main:refs/remotes/origin/main && git diff "$(git merge-base --fork-point origin/main HEAD)" Which calculates the PR diff to main, like you'd see on Github.

Something I've learned about myself in the past few years is to trust my 'spidy senses' on complex problems. They turn out to be right 95%+ of the time but come with 0 rational explanation I can pass on to others. Usually takes a couple days for my brain to catch up.

I'm internally conflicted about using AI tools to code. I want it to be good! But I keep trying claude code in good faith but remain pretty unconvinced. I'm slowly diverging from quite a few of my friends and colleagues who seem are all increasing vibing.