Coding with LLMs
2026.013The bugs are quieter now. Just wrong assumptions buried in correct-looking code.
The bugs are quieter now. Just wrong assumptions buried in correct-looking code.
The legacy codebase runs the business. The migration is on every roadmap. Not this one.
The panel is not comparing the diagram to a reference solution. There isn't one.
What it takes to build a remote engineering center -- and what stays the same when you do it again at a tenth of the scale.
The debate ended when the PM pulled up a graph.
The first migration had a platform on fire. The second has one that works. That is the harder one.
The prep runs out ninety minutes in. The rest is improvised on a floor where nobody leaves.
What a codebase looks like when two people build everything -- 350 commits, and a todo list with two items.
Turning months of git commits into an animated video with Gource and ffmpeg -- then opening the weekly sharing session with it.
Leaving the salary to try building something -- a platform where the unit isn't opinion or memory, but a plan.
Phabricator changed what code review means to me. A note from a few months in.
Our team's Node.js conventions -- error-first callbacks, early returns, callback alignment, and the formatting rules we drilled into every new developer.
Commit history isn't a log of what happened -- it's a narrative you author. Rebase, atomic commits, and the discipline of writing history for the person reading it six months from now.
Ditching WordPress for a custom Node.js blog engine powered by libgit2 -- git as the content store, markdown as the writing format, npm for everything else.
A basement, a barcode scanner, and the moment the dispatch desk stopped waiting.
The training gave me syntax. My first manager gave me taste.