Software Engineering

The One Production System No One Is On-Call For

The development pipeline is the factory floor of software. When it breaks, you’re not making anything. Yet most companies treat it as an afterthought β€” no on-call, no budget, no urgency. This article argues that the pipeline is the most critical production system in any engineering organization, and ignoring it is a recipe for failure.

The Linting Rule That Will Save Your AI from Hallucinating Itself to Death

AI agents rely on structured definition files like skill.md and MCP server descriptions. Linting those files isn’t just about code qualityβ€”it’s the new type checking that prevents hallucinations and infinite loops. Real developers are already building these linters. Ignore them at your own risk.

Stop Treating Specifications Like Separate Documents

Most teams treat specifications as static artifacts that inevitably decay. Instead, embed spec quotes directly into the implementation code, creating a self-verifying, bidirectional link between requirements and execution. This simple practice makes maintenance trivial and coverage checking automatic. No more hunting for where a spec change impacts the codebase.

AI Is the Junior Developer. You’re the Manager. Deal With It.

AI hasn’t freed you from programming β€” it’s promoted you to manager of a brilliant but reckless junior developer. The real skill now is not writing code, but knowing what code to write. As coding gets easier, engineering gets harder. Welcome to the era of the Code Director.

I Tamed AI’s Verbosity with a 50-Year-Old Standard. Here’s How.

AI-generated text is bloated and ambiguous. By forcing AI agents to write in ASD-STE100 Simplified Technical English, we reverse the problem: using extreme complexity to achieve extreme simplicity. The result? Crisp, unambiguous instructions that save time and reduce errors. This isn’t about making AI smarterβ€”it’s about making it shut up and say exactly what it means.

Stop Believing the 10x AI Myth. The Real Number Is 10%.

The AI productivity hype is a dangerous myth. While AI can generate code 10x faster, the hidden costs of verification, debugging, and technical debt reduce net gains to around 10%. This article reveals why the real bottleneck is human judgment, not output speed, and how conservative integration yields sustainable 1.5-2x improvements.

The 15-Line Rule That Could Save Open Source From AI Rot

GCC’s new AI policy β€” a simple 15-line limit on AI-generated code contributions β€” is a brilliant move to protect open-source integrity. It forces human accountability, turning a liability firewall against automated mediocrity. This isn’t about stopping progress; it’s about preventing the rot of the digital infrastructure we all depend on.