Overly structured, workflow-based systems that work with today's models will become bottlenecks tomorrow. Engineers must be prepared to shed abstractions and rebuild simpler, more general systems to capture the gains from exponentially improving models.

In the AI era, foundation models can render complex, custom-built features obsolete overnight. This requires a culture where teams willingly discard their own hard-built IP without ego, accepting their work has a short shelf life.

The "bitter lesson" of AI applies to product development: complex scaffolding built around model limitations (like early vector stores or agent frameworks) will inevitably become obsolete as the models themselves get smarter and absorb those functions. Don't over-engineer solutions that a future model will solve natively.

In the rapidly advancing field of AI, building products around current model limitations is a losing strategy. The most successful AI startups anticipate the trajectory of model improvements, creating experiences that seem 80% complete today but become magical once future models unlock their full potential.

Contrary to the classic engineering rule to "never rewrite," Block's CTO believes AI will make this the new standard. He is pushing his teams to imagine a world where for every release, they delete the entire app (`rm -rf`) and rebuild it from scratch, with AI respecting all incremental improvements from the previous version.

The founder of Stormy AI focuses on building a company that benefits from, rather than competes with, improving foundation models. He avoids over-optimizing for current model limitations, ensuring his business becomes stronger, not obsolete, with every new release like GPT-5. This strategy is key to building a durable AI company.

The underlying infrastructure for AI agents ('harnesses') becomes obsolete roughly every six months due to rapid advances in AI models. At Notion, this means completely rewriting the harness multiple times a year, demanding a culture comfortable with constantly rebuilding core systems and discarding previous assumptions.

With vibe coding, prototypes are cheap and disposable. A critical skill is recognizing when you're iterating on a flawed foundation. Instead of trying to fix a bad start, it's often more efficient to 'nuke it from orbit,' refine your requirements, and generate a new version.

To transition to AI, leaders must ruthlessly dismantle parts of their existing, money-making codebase that are not competitively differentiating or slow down AI development. This requires overcoming the team's justifiable pride and emotional attachment to legacy systems they built.