# software-engineering

As CTOs aggressively push AI coding, software engineers split into two classes: the lazy and the craftsmen. The lazy throw code up, never read it, never test it, never care. The craftsmen carry the whole review burden, watch quality collapse, and eventually become lazy too.

The 2026 data all points one way: AI pushes raw code output up about 4x, but real delivered value only rises about 10%. The gap in between is all review debt. Writing code got cheap; being sure it is right did not. Code review went from a side effect of engineering to its most leveraged front line.

When machines start writing code, the scarce skill is not tool fluency. It is architectural judgment: digging below abstractions, defining boundaries, writing specs, falsifying claims, and deciding where human judgment still matters.

Google Engineering Practices frames code review as code-health work, not a perfection ritual: approve CLs that improve the system, while aligning design, tests, speed, comments, and author habits around maintainability.

Addy Osmani warns that default AI coding workflows help people close tasks, but do not automatically make them sharper. The difference is not whether engineers use AI; it is whether they use it to test and grow their own mental models.

Mitchell Hashimoto's point about Bun moving from Zig to Rust is not that Rust won and Zig lost. The more useful lesson is that programming languages are becoming more replaceable, and developer-tool companies need to manage technical narratives before the internet turns them into faction wars.

Peter Steinberger says OpenClaw often runs about a hundred Codex instances in the cloud. The point is not showing off AI spend. It is testing what software work looks like when review, triage, security, reproduction, benchmarks, and meeting follow-up become always-on agent work.

Garry Tan argues the real breakthrough in AI coding is not speed. It's turning tests, docs, and evals into a forward-only quality ratchet, so every change locks in what the team learned and makes the codebase harder to silently degrade.

Django co-creator Simon Willison gave Lenny's Podcast a broad AI status report: November 2025 as tipping point, coding agents burning him out by 11 AM, Dark Factories, mid-career risk, and the security pattern he calls the Lethal Trifecta.

Mario Zechner wrote a sharp critique of how coding agents are being used in production — compounding errors, zero learning, runaway complexity, and low search recall. His conclusion isn't 'stop using agents' but 'slow down and put human judgment back in the loop.'

Dan McAteer's tweet questions a common leap in logic: if AI automates software engineering, software demand keeps growing, and trained engineers are best positioned to ride the wave — how does anyone conclude that engineers are screwed?

The author benchmarked system SQLite against an LLM-generated Rust rewrite. Even though it compiled and passed all tests, primary key lookups were ~20,000x slower. The takeaway: define acceptance criteria before you talk about AI productivity.

AI writing better code? That "Deep Blue" feeling, coined by Simon Willison & Adam Leventhal (Oxide & Friends), means IBM's chess computer & the color of sadness. It's not just a tech problem, but a psychological crisis for engineers.

Technical debt lives in code, cognitive debt in your brain. As AI writes 80% of code, system understanding drops to 20%. UVic's Margaret-Anne Storey, Simon Willison, & Martin Fowler confirm this isn't a hypothetical future—it's happening now.

Thoughtworks' AI in software retreat: Juniors more valuable, mid-level devs at risk, source code transient, AI agents on org charts. Humans too slow for AI's speed.

Anthropic's 2026 Agentic Coding Trends Report highlights multi-agent adoption, the Papercut Revolution for tech debt, self-healing code, and Claude Code hitting $1B ARR. TELUS and Rakuten case studies show developers shifting from code writer to system orchestrator.

OpenAI co-founder Greg Brockman publicly reveals how OpenAI is transforming to agentic software development internally. By March 31st, agents should become the first resort for all technical tasks. Includes six concrete recommendations, including 'Say no to slop' on code quality.