🫰 1. Where it started
I began my career in IT support — answering calls, resolving tickets, coordinating major incidents, and keeping users productive under pressure.
Over four years, I moved from first-line to Technical Incident Manager. It taught me how to analyze problems, manage chaos, and think in systems — but I wanted to learn how to build them.
⚒️ 2. Learning to build
In 2024, I decided to learn Java. I joined a coding school, started with the basics, and soon realized that writing code was just one part of the bigger picture.
That’s where my roadmap started.
🧩 3. Designing my roadmap
I wanted to build something real, document every decision, and see how a product evolves from monolith to cloud.
So I created a long-term plan.
I designed my learning roadmap with the support of 🤖 AI — not as a shortcut, but as a tool to think broader, plan smarter, and build faster.
In today’s tech world, ignoring AI means missing the biggest leverage new engineers have.
📦 4. The project behind it
To make my roadmap real, I started building a backend application — my sandbox for architecture and automation experiments.
It begins as a clean ♨️Java + Spring Boot🍃 monolith, with REST API and PostgreSQL.
Over time, it will evolve with CI/CD pipelines, Infrastructure as Code, and ☁️ AWS deployment.
🔗 Links
🙌 I’m still early in this journey — if you have any tips, suggestions, or lessons from your own experience, I’d love to hear them.
Top comments (0)