@karpathy Every team I've seen hit this wall at the same moment: local works, now make it real. That's where you discover you're 20% done with the product and 0% done with the infrastructure.
@swyx@jeffreyhuber First it was don't store sessions in files. Then don't store user data in files. Now don't give agents a file system. The lesson keeps finding new students.
@steipete Timing matters more than the change itself. Same breaking change, communicated in advance with context vs. discovered post-update, completely different reaction.
@karpathy What if the IDE abstraction breaks though? Assembly to high-level kept the same mental model. Agent outputs might be too large and too non-deterministic to review the way we review code.
@GergelyOrosz The Scrum Master question is a proxy for a bigger one: who made this role necessary? If it's there to manage coordination that good communication would solve, AI won't kill it. The next reorg might.
@marclou 1M impressions from a vibe-coded site is a strong signal that content and usefulness matter more than packaging. The bar shifted, not the principle.
@GergelyOrosz@mitchellh Counterpoint to #8 though: two years ago, hiding from social media meant heads-down building. Now it might mean you're using AI to do what Twitter used to. Hard to tell the difference anymore.
@__karnati love this series, real-world analogies is how system design should be taught. I've been building https://t.co/JlOL9zEDBg for this, interactive canvas to map concepts visually. would be cool to see your breakdowns as explorable boards
@pulkit_mittal_ The gap isn't knowing all 10. It's knowing which one is biting you during an incident. Most engineers can define P99 latency; fewer know what to do when it spikes at 3am.
@simonw Had this exact failure mode before agents existed. Someone drops 1200 lines, 'review when you get a chance.' The diff is readable. The reasoning behind it isn't.