In a 1983 meeting with the Macintosh team, Steve Jobs reportedly said, “A players hire A players. B players hire C players. Do you get it?”
This pattern applies everywhere, not just hiring. If you don’t hold the line, it’s a downward spiral.
Today I was discussing documentation practices with Claude. I never defined a documentation standard. Yet documentation behavior manifested anyway. I often push back in reviews, but the onslaught of shitty documentation never stops and I get tired. During an audit, Claude reported:
Three Sonnet reviewers read each internal page against the code it describes. Of 19 pages, all 19 came back delete. Nothing was judged worth keeping as a page.
Most restated the code or had gone stale. One described a function signature that has since changed; another gave a mount path the Environment reference contradicts.
Many were history: migration numbers, “remaining implementation” lists, dated measurements. Six carried a few sentences the code could not tell you. I moved those into doc comments where the code lives.
At some point an agent invented the idea of creating a document describing a feature’s implementation. Other agents saw that as a codebase standard and did it too. If that’s what we’re doing, why not create documentation for other stuff too? Soon I had directories full of deployment notes and future plans.
I regret to inform you this also holds for code. Once an agent takes a shortcut, every other agent sees shortcuts as acceptable. C players from here on out.
None of this is new with AI. We’re all just speed-running decades of software engineering experience. AI is the ultimate cargo cult programmer (Jargon File, 1991):
A style of (incompetent) programming dominated by ritual inclusion of code or program structures that serve no real purpose.
Hold the line.