Opinions.
The tracks are organised by your stage. These aren't. This is the case for a specific, arguable position, held long enough to write down, not softened to survive a comment section.
Where a lesson tells you what to do at twenty engineers, an opinion tells you why the ground moved under all of it. Disagree with it. That's what it's for.
Intent architecture
For thirty years, the gap between what an organisation actually wants and what it writes down got closed by a person, every time, without anyone noticing it was happening. The moment a system is doing the reading instead of a person, that gap stops closing itself.
Includes a toolAdapted from After the PromptThe prompt tax
Every recurring prompt looks like a productivity win because you're measuring the wrong side of the ledger. The real cost isn't building the workflow. It's operating it, every week, for as long as the team runs it.
Includes a toolThe monolith default
Ninety percent of production software would ship faster and break less as one deployable than as the distributed system most teams reach for instead. Not for a first year before graduating to services. As the actual architecture, for as long as the product exists.
The Kubernetes tax
Kubernetes solves real problems that almost no company under thirty engineers actually has yet. The bill isn't the weekend it takes to set up. It's every subsequent debugging session running through a layer nobody on a small team fully understands.
The agentic prerequisite
Every conversation about getting ready for agentic development is about the tool. The variable that actually decides whether it goes well is whether your test suite still tells the truth, and agents don't create that discipline. They just find out immediately whether you have it.
Nobody has to approve the agent's merge
The mandatory-human-approval rule most orgs wrote this year is theatre. What gates a change to main was never the signature at the bottom of the pull request, it was the machinery underneath it, and the only thing agents changed is that the difference is now visible.
Adoption isn't a result
Percentage of engineers active weekly, percentage of merged code AI-generated, prompts per head. Every one of those is a utilisation number, and optimising utilisation is how organisations made themselves slower for decades before any of this arrived.
Your AI bill is a design defect
Token spend scales with decisions inside your workflows, not with how many people hold a licence. That makes it an engineering problem arriving in finance's clothing, and every control finance reaches for first is aimed at the wrong variable.
The invention floor just dropped
The scarce skill was never having the idea. It was the distance between having one and putting it in front of a stranger, and for a huge class of ideas that distance now runs to a weekend instead of a headcount. Function doesn't matter. Finishing does.
Never rewrite was a budget rule
The rule held for twenty-five years because rewriting cost human-years. That bill has collapsed and the other one hasn't moved, which means the thing that used to stop bad rewrites has quietly stopped stopping them.