Why write code in 2026
softwaredoug.com · 900 words · saved by 1 readers
A bunch of reasons to write code in 2026
It’s our job to build the software factory - not just the software. Software engineers maintain the assembly line allowing anyone to prompt for a change and ship immediately. We set up the infrastructure that makes agents successful. We act proactively through prompts (skills, AGENTS.md, knowledge bases etc). We protect software reactively through automated evaluation (tests, linting, type systems, evals, other AI, etc). It all keeps the agent on track. Even a stupid model, with fresh context, can work within these constraints and produce a good-enough change. It starts to seem ridiculous…
saved by
related reading
- Why We Built Our Own Background Agentbuilders.ramp.com
- Thoughts on slowing the fuck downmariozechner.at
- Code was our medium for thoughtwattenberger.com
- claude code is not making your product betterethanding.substack.com
- dex (@dexhorthy) on Xx.com
- Thoughts on slowing the fuck downmariozechner.at
- Would you fly on an AI-coded plane | Hackle's bloghacklewayne.com
- Your job is to deliver code you have proven to worksimonwillison.net
- The Case for Software Craftsmanship in the Era of Vibes — Zed's Blogzed.dev
- Code is cheap. Show me the talk. - nadh.innadh.in
- lauren (@poteto) on Xx.com
- Now – Updates from the Linear teamlinear.app