Architects Will Thrive in the Age of AI
Why Enterprise and Solution Architects Will Outlast Coders
Eric Schmidt recently said that most programmers could be replaced by AI in the next year. That’s a big statement—and honestly, I don’t think he’s wrong. But as someone who’s worked across enterprise and solution architecture roles for years, I see this shift a bit differently.
From my experience, this isn’t the end of programming—it’s a turning point. And it’s not a threat to architecture. If anything, it’s going to make what we do even more valuable.
Because when code becomes a commodity, the people who can design the system, align it to business goals, and lead the change—that’s where the real value sits.
This article is my perspective on where we’re heading, and why I believe enterprise and solution architects will have more opportunities—not fewer—in the age of AI.
The Age of AI-Generated Code
What Eric Schmidt Got Right
AI isn’t just writing code—it’s improving it too.
Tools like GPT-4, Claude, and Gemini are already taking over repetitive programming tasks.
We’re entering a time where the value of traditional coding is changing—fast.
As someone who has worked closely with development teams, I’ve seen this shift up close. AI tools are speeding up prototyping, testing, and even bug fixing. In many teams, the most repetitive parts of programming are already being offloaded. The pace of change is real.
Where That Leaves Programmers
Repetitive tasks are going out the window.
Engineers who focus only on code, without understanding the broader goals, will find it hard to compete.
The market will favour developers who can think at a system level, solve real business problems, and work across disciplines.
From my point of view as an architect, we don’t need more coders—we need smarter systems, better design, and tighter alignment with business strategy. That’s where architects shine. And that’s why I believe those who think holistically—who understand people, process, and tech—will thrive in what’s coming next.
Strategy Still Needs Humans
Coders Build. Architects Lead.
As an Enterprise Architect, I know the real work starts long before anyone writes code.
Architects shape the system’s direction—we align it with business goals, security, data flow, and team capacity.
AI might speed up delivery, but it doesn’t know your stakeholders, constraints, or organisational priorities.
I’ve seen projects where everyone jumped straight into coding, thinking the faster they shipped, the better. But without a clear strategy and structure, they just built faster… in the wrong direction. That’s where architecture makes all the difference.
The Human Role in Business Change
AI doesn’t sit in a boardroom balancing budgets or resolving conflicts across teams.
It doesn’t assess risk across a portfolio or align technical debt with strategic goals.
These are human conversations—and they shape the success of every major initiative.
Whether we’re talking cloud migrations, data strategy, or GenAI adoption, architects translate vision into execution. We don’t just design systems—we create shared understanding. And no AI is doing that job yet. From my experience, the future belongs to those who can lead both people and technology together.
The Rise of Enterprise and Solution Architects
Enterprise Architects Will Drive Strategy
From what I’ve seen in the field, the more advanced the technology becomes, the harder it is to connect it back to business value. That’s exactly why Enterprise Architects are needed more than ever.
We don’t just approve tech choices—we ask, “Why does this matter to the business?”
AI introduces new risks, new costs, and new opportunities. Sorting through that complexity requires human judgement.
Our job is to make sure every initiative—whether AI, data, cloud, or cyber—fits into the bigger strategic picture.
You can’t outsource this kind of thinking to a tool. It takes experience, context, and clear communication across the business. That’s what separates architecture from engineering.
Solution Architects Become Orchestrators
Solution Architects are often closest to delivery—but their role is expanding too.
It’s no longer about just selecting tools or writing specifications.
It’s about orchestrating the people, platforms, and workflows needed to deliver outcomes that matter.
In my projects, the best Solution Architects are the ones who can talk to developers in the morning and present to executives in the afternoon. That range is critical as we bring AI, cloud, APIs, and legacy systems together under one umbrella.
And as systems keep getting more complex, this ability to “orchestrate” will become the key to execution. That’s where I believe real leadership in architecture is heading.
What You Should Focus on Next
If You’re a Programmer Today
If I were starting out as a programmer now, I’d be thinking bigger than syntax or frameworks. The future’s shifting, and fast.
Get curious about how the business works—not just the codebase.
Study architecture patterns, integration strategies, and how products are monetised.
Learn to talk in outcomes, not just implementation details.
I’ve seen talented engineers get left behind simply because they didn’t make that mindset shift. The ones who do evolve into architects, product leads, or founders.
If You’re in Leadership
One of the biggest mistakes I see in AI strategy is bringing in architects too late—once the tools are already chosen and the direction is locked in.
Invest early in strategic architecture capability—not just in hiring more engineers or data scientists.
Give architects a voice in planning, budgeting, and solution shaping.
AI isn’t just a technology problem. It’s a business transformation opportunity. And transformation needs architecture from day one. I’ve been in rooms where one architect at the table saved a project from going in the wrong direction before a single model was trained. That’s the kind of shift we need.
Conclusion: We’re Not Replacing Architects Anytime Soon
AI is shifting how we work—but not in the way most people think. Writing code isn’t the hard part anymore. That’s becoming the easy bit.
The real challenge is knowing what to build, why it matters, and how it fits into the bigger picture.
As an Enterprise Architect, I’ve seen firsthand how much strategy and structure matter—especially when the technology keeps evolving faster than the business can catch up. That’s not going away.
We don’t need more tools—we need clearer thinking.
And that’s exactly what architects bring.
If you’re looking to stay relevant, don’t just learn a new tool.
Learn how to ask better questions, connect the dots, and guide people through change.
That’s the future I see—and it’s one I’m ready to help shape.
If your team is exploring how to stay relevant and strategic in the AI age, let’s connect. I help leaders reimagine their architecture to stay future-ready—without losing clarity, structure, or business value.
Whether you’re planning your AI roadmap, restructuring your tech teams, or simply trying to cut through the hype, I bring practical architecture thinking grounded in real business outcomes.
Message me if you’d like to chat.