Field notes
Updates, guides, and insights on Specification-Driven Development.
Most people discussing AI tools at work are mixing up categories that solve different problems, and the vendors are not helping. Part one of a series sorting out the layers: what the four browser-based full-stack builders do, and the wall they all hit in the same place.
Gartner says poor architectural choices will push half of GenAI projects over budget through 2028. Its own August research points somewhere else, at agentic workflows costing five times more per task because agents run longer and retry more. Scope drives the bill, and a spec is what bounds it.
Days after Anthropic said Claude would start watermarking everything it writes, a free GitHub tool showed up to strip those marks. Its own README is more honest than the hype around it, and the real fix it points to isn't a rewrite script.
Anthropic is embedding an invisible, machine-readable signal into everything Claude generates, from prose to Claude Code output, to comply with the EU AI Act. For engineering teams, the watermark itself matters less than what it can and can't actually prove.
Microsoft's Project Polaris replaced GPT-4 Turbo as GitHub Copilot's default model this month, with gains landing unevenly across languages. Teams with no fixed baseline to test against won't notice a regression until it's already in production.
Meta launched Muse Code, a terminal-based coding agent, with a discounted 'contributor' tier that trades a lower price for the right to train on your prompts and completions. That's a data licensing decision dressed up as a pricing plan.
Wiz's GhostApproval disclosure showed six major AI coding assistants approving file writes based on a filename the agent never actually touched. The fix is scoping what an agent can touch before it runs, not asking a human to referee each write as it happens.
Meituan just open-sourced a 1.6-trillion-parameter coding model with a million-token context window. It won't fix the thing actually breaking your codebase, because model capability was never your bottleneck. Intent is.
Singapore's IMDA and NIST both shipped agent governance frameworks this year demanding identity, audit trails, and accountability for autonomous coding agents. Teams running spec-driven development already have all three - they called it a spec instead of compliance.
AI tools write 41% of all code and 92% of developers use them daily, yet a controlled study found experienced developers took 19% longer to finish tasks with AI. The bottleneck moved from typing to alignment, and spec-driven development is how teams are closing the gap.
FDE job postings are up roughly 800% year-over-year. The skill companies are actually paying for isn't coding speed - it's the discipline of turning ambiguity into a structured build plan fast. That discipline has a name.
Prompt quality in large codebases isn't a skill problem - it's a context problem. Here's why specification-driven development changes the equation.
When Anthropic's internal Claude Code system prompts leaked, developers got an unfiltered look at how AI coding agents are actually instructed. Here's what it reveals about the state of spec-first development.
A practical comparison of SpecPilot and GitHub Spec Kit for teams adopting Spec Driven Development with AI coding agents. What they share, where they differ, and which fits your team.
Beyond the tools: how Specification-Driven Development and the BMAD methodology differ in their fundamental philosophy, developer role, and approach to structured AI collaboration.
Exploring the growing disconnect between AI-assisted productivity and the deep sense of creative accomplishment that defines great software engineering.
Why we are launching a markdown-first blog for SDD updates and practical guides.