I gotta trick myself into paying attention to AI agents, or else I miss their regular mistakes.
I have a little plan-editing workflow with Claude Code that works well: at every single plan prompt, hit ctrl-g to “open in editor”, and leave comments directly in it.
huonw.github.io/blog/2026/02...
literally exactly what I was searching for:
magit-insert-worktrees improves status buffers by @huonw.bsky.social huonw.github.io/blog/2025/12...
For better, my colleagues have been very straight-faced, and continue to interact with it normally. No-one has questioned its behaviour.
For worse, I haven’t seen it make a pun yet. Not even a bad one.
A screenshot of a code review comment, that says: Estimated code review effort 🎯 2 (Simple) | ⏱️ ~8 minutes Blimey, what an unholy jingle-bell of a change! This commit's been very naughty indeed - like putting coal in Santa's config file instead of Christmas cheer! The linting sleigh won't be flying anywhere with this one on the naughty list. Makes you wonder if someone's been hitting the eggnog a bit too early this festive season! 🎅✨
A screenshot of a code review comment: 🎅 Santa's curl command could get stuck in the chimney forever! Your curl command is missing a timeout! Without --max-time or --connect-timeout, the script could hang indefinitely if Slack is slow or unreachable, blocking your entire build pipeline like a stuck sleigh! For a critical notification hook, you should add reasonable timeouts to ensure the build can continue even if Slack is having a bad Christmas. • 🎄 Recommended fix
For better or worse, we use an AI review tool at work.
I gave it global “speak like Santa” and “make Christmas puns” instructions last week. It is both conscientious and heavy-handed in following that critical prompt.
I have spent too long guessing at the exact configuration of HTTP request URLs, headers, and data implied by someone's description of a failure... Browsers offer a "Copy as cURL" superpower that I enjoy using and maybe you would too!
huonw.github.io/blog/2025/08...
I file too many bugs and triage a whole lot too. Strangely, shell heredocs are kinda useful to share executable minimal reproducers
huonw.github.io/blog/2025/04...
Do you need match fallthrough in your Rust code? Do you want some cursed code?
Labelled breaks are what you need!
huonw.github.io/blog/2025/03...
I’ve made a habit of using tee -a $GITHUB_… for GitHub Actions CI “commands”, instead of >> $GITHUB_… . It improves debugging/introspection seemingly for free.
huonw.github.io/blog/2025/02...
Heya, thanks!
The code snippets/concepts in the talk itself are the only public ones I have to hand right now.
I’m happy to answer any questions, let me know.
Haha, thanks. My “slides” were just a bunch of tabs/windows, so it would’ve been extremely triumphant if macOS managed to put it all back in the right place!
At least #PyConAU is a kind crowd. I heard/felt the sympathy from the crowd.
Filed under “don’t need to do again”: laptop crashing hard, while speaking in front of a few hundred people… all my visuals were there!
I'm speaking at PyCon AU this weekend, about how we run our tests against (real) Postgres: 2024.pycon.org.au/program/UKJB...
