I started on the sysadmin side: customer environments, incidents and the daily reality that systems fail. With no traditional CS background and no predefined path, I needed to extract value from every task, piece of advice, mistake and incident. This lightning talk is an honest account of how that shaped my move into software engineering. Sometimes it was an advantage (debugging discipline, failure-mode thinking and respect for blast radius), sometimes friction (perfectionism, fear of code and collecting technologies without shipping). I’ll reflect on the moments that changed how I learn and how I work, including two accelerators: AI, which shortened the path from “I don’t get this algorithm” to “I can apply it,” and mentorship, which turned scattered effort into focused progress by challenging and correcting mental models. The goal isn’t to prescribe a path, just to share real tradeoffs, mistakes and turning points from a non-traditional route into engineering.