Why I Blog: My Three Strategic Goals as a Technical Architect
This blog is more than just a writing exercise; it is a commitment to a set of core principles that define my philosophy as a technical leader. Everything I publish here is in pursuit of three strategic goals.
This is the “Why” that drives me to carve out time for hands-on work and share my experiences:
-
Reconnecting Architects to Implementation
We are former engineers who love solving problems, but years in the architecture space can lead to abstraction from implementation details. This blog is my way of figuring out and showing other architects how to stay hands-on.
- The Benefit: Going through the implementation process is the crucial step in evaluating technology. It quickly reveals where marketing hype ends and real-world complexity begins, ensuring our decisions are practical and ultimately making us better architects.
-
Career Accountability and Marketability
The GenAI revolution is rapidly making the technical market competitive. This blog serves as a mechanism to:
- Keep Myself Accountable: It is a public commitment to continuous learning and upskilling in my career.
- Showcase My Knowledge: It allows me to build a portfolio that demonstrates what I can do and how I think, helping me maintain my competitive edge.
-
Making Engineers’ Lives Easier
As a technical leader, my responsibility is to reduce friction and set my engineers up for success.
- Empathy Through Experience: Being hands-on during implementation is critical for building empathy for the engineering team.
- Responsible Leadership: Making good decisions with technology, and using tools like GenAI responsibly, is how we reduce mental load and stress, leading to happier, more successful engineers and teams.
This blog is my commitment to bridging the gap between high-level strategy and low-level code, ensuring that every architectural decision I make is informed by current, real-world development experience.