Pinned post
Important parts of my story. In case you're interested.
@T1GlistenerElf It's a pretty long story, but here's some salient bits.View quoted post on X
@cobblepott__
Pinned post
@T1GlistenerElf It's a pretty long story, but here's some salient bits.View quoted post on X
CEDH be like:View quoted post on X
I’ll cast force of will on your spell
“But what if you didn’t?”
I think software engineering is about to develop a new kind of technical debt.View quoted post on X
Comprehension debt.
Here's how it happens:
A developer asks an AI agent to build a feature.
The agent creates the database schema, APIs, frontend components, tests and documentation.
Everything works.
The PR is merged.
But the developer only understands 30% of what was actually changed.
Now imagine doing this for 20 features.
Eventually, you have a codebase that works, but nobody on the team has a complete mental model of it.
The scary part isn't that AI writes bad code.
It's that AI can write perfectly acceptable code faster than a team can understand it.
I think future engineering teams will need to measure not just how quickly they ship, but how much of their codebase they can still explain and maintain.