I’m a Cloud Enterprise Architect with a background that spans software development, product ownership, and enterprise architecture.
My career started close to the code. I’ve worked as a developer with C#, Java, and PHP, building software and learning firsthand what it takes to turn ideas into systems that actually work. Later, as a Product Owner, I moved closer to the business side working with users, stakeholders, and teams to turn problems into products and priorities into outcomes.
Today, I work as a Cloud Enterprise Architect, where I focus on the bigger picture: how technology, architecture, people, and business requirements come together to create scalable and sustainable solutions.
My main area of interest is cloud computing, particularly Microsoft Azure. I enjoy exploring cloud architecture, platform capabilities, security, integration, governance, and the many decisions that sit behind a successful cloud adoption. I’m especially interested in the practical side of architecture not just what a platform can do, but when and why you should use it.
More recently, AI has become a major part of my professional curiosity. Tools such as GitHub Copilot and Claude are changing the way we write software, solve problems, work with information, and think about productivity. I’m interested not only in the technology itself, but also in what happens when AI becomes part of everyday engineering and enterprise workflows.
That combination software development, product thinking, cloud architecture, and AI shapes how I approach technology.
I like understanding systems from different perspectives. As a developer, I learned to care about implementation. As a product owner, I learned to care about value and people. As an architect, I’ve learned to connect those perspectives and think in terms of systems, trade-offs, constraints, and long-term consequences.
This blog is where I document what I learn along the way.
You’ll find posts about Azure and cloud architecture, AI and developer tools, software engineering, architecture patterns, technology experiments, and lessons from real-world projects. Some posts may be deep technical dives; others may be about an architectural decision, a new tool, or simply something I found worth thinking about.
I don’t write this blog because I have all the answers. Quite the opposite.
I write because exploring technology is easier when you make your thinking explicit and because something that took me several hours to figure out might save someone else a few hours.
So think of this site as my technical notebook, with the door left open.
Keep learning. Keep building. Keep questioning.