Posts tagged Software development
Posts on software engineering: simple design, testing, error handling, TypeScript and AdonisJS, and the habits that keep code easy to change. 19 posts with this tag.
2026
- Agent quality gate, part 5
40 pull requests in one evening with an agent: the decisions I kept
One evening, five repositories, 40 merged pull requests and 7 releases with a coding agent. The speed came from the agent. What made it safe was the human in the loop: plans, break points and the decisions it never made alone.
- Agent quality gate, part 4
Prove it: measuring that a refactor changed nothing
An agent says its refactor doesn't change the rendering. I asked it to prove it: every element, 46 computed styles, 16 pages, 0 differences. The measurement had to be tested first.
- Agent quality gate, part 3
The squash merge that resurrected a release
A release pull request merged with squash brought back a changeset that had already shipped. Six incidents from one evening of setting up a canary-to-main flow, and the rule each one produced.
- Agent quality gate, part 2
One stack, five repos: my setup and workflow with coding agents
Vite+, pnpm, a shared quality gate and a canary-to-main release flow: the setup behind my five repositories, and the workflow I follow with coding agents.
- Agent quality gate, part 1
Your coding agents need feedback in one second, not one minute
I asked whether SonarQube could review my agents' pull requests. The answer was a stack of checks ordered by speed: hooks for fast feedback, CI for enforcement.
-
An always-on box for my coding agents, on Railway
How I set up a cloud server to drive Claude Code and Codex from my phone: Railway, T3 Code, signed commits, Vite+ as the toolchain, and a hard line between client and personal code.
- Engineering agents, part 7
The toolkit: Agent Skills from this series
Every Agent Skill from the engineering-agents series, grouped by step, on one page.
- Engineering agents, part 6
Don't break what works: Chesterton, Hyrum, and the supply chain
The simplifier agent removed 400 lines. Another agent added a dependency that pulls in forty others. Each change looked harmless.
- Engineering agents, part 5
Scale without chaos: Brooks, Conway, Lehman
Six agents in parallel, three agents split by technical layer, six months of nobody deleting anything. Three laws saw it coming.
- Engineering agents, part 4
Verify: test first, mutation gates, independent review
"47 tests added, all passing, 94% coverage." Then the same agent reviews its own code and finds nothing.
- Engineering agents, part 3
Make wrong code impossible: structure, deep modules, contracts
A 180-line function, a rounding helper imported from eleven files, an optional discount that can be -15. None of these agents made a syntax error.
- Engineering agents, part 2
Start right: thin slices, one job per agent, no premature optimization
You ask an agent to "build the billing module." Twenty minutes later, it has generated 3,000 lines, and nothing compiles.
-
195 repos, one map: the meta-repo, and why your AI agents need it
The meta-repo keeps many repositories but gives you one place to clone, run and read them. overrepo takes the idea to ~200 repos, and writes a map your AI agents can actually use.
- Engineering agents, part 1
Why fundamentals still matter: your agents aren't dumb, they're amnesiac
On Monday, you explain to an agent that a 200-line function is not acceptable. On Tuesday, a fresh agent writes one with 250 lines.
-
Hacktoberfest 2026 isn’t about PRs anymore, and that’s good news
Pull requests no longer count toward Hacktoberfest rewards. The scoreboard moved to learning and building with open-weight models, stickers included.
-
I Built a SaaS with AdonisJS 7, and I Loved It
I open up the real engineering decisions behind my latest SaaS, built with AdonisJS 7, Inertia, and Vue 3.
-
The Boy Scout Rule: Leave Code Better Than You Found It
"Always leave the campground cleaner than you found it." (The Boy Scouts) Robert C. Martin adapted...
-
The 4 Rules of Simple Design: A Practical Guide with TypeScript
Kent Beck introduced the 4 Rules of Simple Design as part of Extreme Programming in the late 1990s....
Nothing matches that search. Try another word, or clear it.