Fourteen years ago, I wrote my first Spring Boot service and thought I'd figured out software engineering. I hadn't, of course — but that naive confidence carried me through healthcare systems, workforce management platforms, payment gateways, and eventually into the world of event-driven architecture and distributed systems. Each phase taught me something the previous one couldn't, and looking back, the thread connecting all of it is clearer than I expected. The shift to AI-assisted development didn't feel like a pivot — it felt like a natural extension. Years of working with complex systems taught me how to decompose problems, design for failure, and think in abstractions. Those same skills turned out to be exactly what you need to work effectively with agentic AI tools. The engineers who struggle with AI aren't lacking prompt skills; they're lacking the systems thinking that comes from years of building things that break in production. This post traces that journey — from junior Java developer to technology consultant and AI builder — and distills the lessons I'd share with my younger self. If you're a mid-to-senior engineer wondering whether the AI wave is relevant to your career, this is my honest take.

The Foundation: Java, Spring, and Learning to Build

The Inflection Point: Distributed Systems and Event-Driven Thinking

The AI Chapter: From Consumer to Builder

What I'd Tell My Junior Self

What's Next

Follow my journey on LinkedIn for regular posts on backend engineering and AI-assisted development.