To help developer transition to Solution Architect,to make great Solution Architect , to make a life-long career out of IT.You can connect with me via @ybbest https://www.linkedin.com/in/ybbest/
All content for Solution Architect Show is the property of Ben Yu and is served directly from their servers
with no modification, redirects, or rehosting. The podcast is not affiliated with or endorsed by Podjoint in any way.
To help developer transition to Solution Architect,to make great Solution Architect , to make a life-long career out of IT.You can connect with me via @ybbest https://www.linkedin.com/in/ybbest/
Ben opens by acknowledging Bernard’s pivotal influence on his own career path, especially a memorable meeting where SharePoint development was declared “dead,” prompting Ben to pivot toward architecture.
Bernard reflects on that moment and shares his own journey, starting as a developer working with 3GL, VB, and client-server systems, eventually transitioning into architecture through consulting and business engagement.
Why Architecture?
Bernard was drawn to architecture due to his interest in design correctness, foresight, and creating long-term value.
He emphasizes that architecture is about making big technology decisions and acting as an insurance policy for organizations navigating rapid tech evolution.
Key Philosophies
Context is king: Bernard stresses the importance of understanding how a business operates and makes money—something he encouraged Ben to consider early in his enterprise architecture role.
Architects must bridge technical capability with business strategy, enabling scalable and executable solutions.
Upskilling & Staying Relevant
Bernard shares his approach to staying current:
Read McKinsey articles to track technologies moving from emerging to adopted.
Use Gartner’s hype cycle to understand tech maturity.
Follow platforms like InfoQ for practical insights.
Leverage tools like ChatGPT to explore and learn faster.
He’s not interested in tech for tech’s sake—he values applied technology that solves real problems.
Self-Awareness & Team Enablement
Bernard humbly admits he wasn’t the best developer, but his strength lay in providing context and clarity to help others make better decisions.
He views architecture as a way to codify ambition and scale, enabling teams to execute effectively.
Staying Current & Validating Information
Bernard emphasizes that keeping up with technology trends is a team effort, not a solo task. Architects must collaborate with engineers and peers to stay informed.
He warns against “tech for tech’s sake,” sharing an example where AI was added to a project without clear business value—echoing research showing many AI pilots fail due to lack of purpose.
On validating information, Bernard advises:
Don’t blindly trust any source—including McKinsey, Gartner, or AI tools like ChatGPT.
Use multiple sources and triangulate insights.
Run technical spikes to test hypotheses and assess real-world applicability.
Understand the long-term implications of adopting new tech, especially regarding technical debt and risk acceptance.
Advice for Developers Breaking into Architecture
Bernard acknowledges the challenge: transitioning from individual contributor to someone who thinks broadly across business and technology.
Key advice:
Learn how the business operates and how it makes money.
Understand the role of technology in enabling business models.
Avoid the “ivory tower” trap—stay grounded and collaborate with those executing the...
Solution Architect Show
To help developer transition to Solution Architect,to make great Solution Architect , to make a life-long career out of IT.You can connect with me via @ybbest https://www.linkedin.com/in/ybbest/
