Matthew Kolnicki

When I was deciding what to study in college, programming was a practical choice more than a clear passion. I had done well in school, and software engineering looked like a stable, valuable path. That mindset helped me get started, but it could only take me so far.

After graduation, I was fortunate to land a role quickly despite having no formal experience. It was the first company that interviewed me, and I am still grateful for that opportunity. But about a year in, I found myself questioning whether I had chosen the right path.

I worked late nights and weekends, constantly feeling like the gap between my peers and me was growing instead of closing. I became overly focused on output and speed, but I was not taking time to reflect on architecture, tradeoffs, or how to solve harder problems over time. I was shipping code, but not developing as an engineer.

That realization changed how I work. I started slowing down enough to study fundamentals, write clearer code, ask better questions, and learn from feedback instead of avoiding it. Do what you are good at, focus on the aspects you enjoy, and the passion will follow. Over time, I became more confident in backend systems, data workflows, and product-minded engineering decisions. I still value consistency and discipline, but now I pair them with deliberate learning.