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.
Related Insights
Don't view AI as just a feature set. Instead, treat "intelligence" as a fundamental new building block for software, on par with established primitives like databases or APIs. When conceptualizing any new product, assume this intelligence layer is a non-negotiable part of the technology stack to solve user problems effectively.
The ultimate vision for AI in product isn't just generating specs. It's creating a dynamic knowledge base where shipping a product feeds new data back into the system, continuously updating the company's strategic context and improving all future decisions.
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.
The most significant productivity gains come from applying AI to every stage of development, including research, planning, product marketing, and status updates. Limiting AI to just code generation misses the larger opportunity to automate the entire engineering process.
Don't just sprinkle AI features onto your existing product ('AI at the edge'). Transformative companies rethink workflows and shrink their old codebase, making the LLM a core part of the solution. This is about re-architecting the solution from the ground up, not just enhancing it.
Block's CTO argues that LLMs are a wasted resource when they sit idle overnight and on weekends. He envisions a future where AI agents work continuously, proactively building features, running multiple experiments in parallel, and anticipating the needs of the human team so that new options are ready for review in the morning.
Features built to guide AI agents, like an explicit "plan mode," will become obsolete as models become more capable. The Claude Code team embraces this, building what's needed for the best current experience and fully expecting to delete that code when a new model renders it unnecessary.
In the fast-paced world of AI, focusing only on the limitations of current models is a failing strategy. GitHub's CPO advises product teams to design for the future capabilities they anticipate. This ensures that when a more powerful model drops, the product experience can be rapidly upgraded to its full potential.
Non-technical founders using AI tools must unlearn traditional project planning. The key is rapid iteration: building a first version you know you will discard. This mindset leverages the AI's speed, making it emotionally easier to pivot and refine ideas without the sunk cost fallacy of wasting developer time.
The Browser Company's Dia browser was built with the conviction that AI models would rapidly improve. Core features like "memory" were impossible, killed, and then revived just before launch when a new model suddenly unlocked the capability, validating their forward-looking bet on the technology's trajectory.