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
- 2x, not 10x: coding with LLMs in 2026obryant.dev
- Software Engineering fundamentals matter more than everrhonabwy.com
- The Eternal Sloptember | the singularity is nearergeohot.github.io
- Thoughts on slowing the fuck downmariozechner.at
- Software Engineering in the Age of AIadiamond.me
- AI is removing the middle class of software engineeringblog.florianherrengt.com
- Code was our medium for thoughtwattenberger.com
- Your job is to deliver code you have proven to worksimonwillison.net
- Would you fly on an AI-coded plane | Hackle's bloghacklewayne.com
- claude code is not making your product betterethanding.substack.com
- Don’t Outsource Your Thinkingteltam.github.io
- Thoughts on slowing the fuck downmariozechner.at