When I first stumbled across Bolt.New, I thought it was just another nifty tool for developers—a way to spin up projects faster. Little did I know, it would become my wake-up call to a rapidly approaching future where developers, as we know them, might not exist.
(If you’re unfamiliar with Bolt.New, I made a video about it, which you can find at the top of this blog. Watch it for some context before diving in.)
The Day It Clicked
It started innocently enough: I was testing Cursor, an AI-powered coding assistant, expecting it to handle basic suggestions or boilerplate code. But as I worked through a project, Cursor began to do more than assist—it started making logical leaps. It wasn’t perfect, but it was shockingly close.
What struck me wasn’t just Cursor’s ability to complete tasks but the potential for where this technology is heading. As I watched it refactor code, anticipate architectural decisions, and suggest optimisations, I realised:
In two years, the role of the developer could look entirely different.
The Evolution of Development
Right now, AI tools like Cursor, GitHub Copilot, and Bolt.New are “assistants.” They take the grunt work out of coding, freeing us up to focus on strategy and creativity. But the next phase is already on the horizon.
In the near future, we won’t be writing code at all—at least, not in the traditional sense. Instead, we’ll oversee teams of AI agents working together to:
- Generate apps, websites, and systems architecture.
- Debug and optimise performance.
- Build features based on plain-language instructions.
The developer’s role will shift from “creator” to “curator.” We’ll be the ones reviewing, fine-tuning, and approving the work AI does for us.

Why This Is Both Scary and Exciting
On the one hand, this is exhilarating. Imagine how much faster we’ll be able to ship products, iterate on ideas, and scale businesses. Developers will become orchestrators of creativity, leveraging AI as a tool to do what was once unthinkable.
On the other hand, it’s undeniably unsettling. The skills we’ve spent years honing could become obsolete. The demand for deep coding expertise may give way to a new kind of technical literacy—one focused on managing AI teams, ensuring ethical practices, and understanding systems at a macro level.
The Tipping Point: Two Years Away?
Looking at tools like Cursor today, I’d estimate we’re two years from a tipping point. By then, AI will likely be capable of:
- Building complete applications with minimal human input.
- Designing sophisticated systems based on natural language prompts.
- Generating codebases that are not only functional but also efficient and secure.
Humans will still be in the loop, but more as decision-makers than doers. The focus will shift to creativity, problem-solving, and setting the vision for AI to execute.
Preparing for the Future
If you’re a developer, don’t panic. Instead, get curious. Now is the time to:
- Learn to work with AI: Explore tools like Cursor, GitHub Copilot, and Bolt.New to understand their capabilities.
- Adapt your skill set: Focus on high-level architecture, system design, and understanding how to collaborate with AI.
- Embrace creativity: As AI handles the technical heavy lifting, your ability to think creatively and strategically will set you apart.

How are you spending your time?
Is it on the things that make your business money? Or is it on... boring repetitive tasks that don't directly generate revenue?
Learn MoreFinal Thoughts
The idea of developers becoming “obsolete” might feel jarring, but it’s not the end—it’s an evolution. The tools we have today are just the beginning of a seismic shift in how software is created.
Yes, it’s a little scary. But it’s also incredibly exciting. We’re on the brink of a future where our ideas can come to life faster than ever before, with AI as our partner rather than a competitor.
The only question is: Are you ready to embrace the change?
Let me know your thoughts in the comments—or better yet, let’s chat about it on LinkedIn or in my upcoming video series. This is a conversation worth having, and I’d love to hear your perspective.
Leave a Reply