Every so often someone asks me, almost with pity, whether I am not tired of this by now. Or, more politely, why I never chased the next rung, manager, director, the corner office. And it is not that I stood still. If you look at my path, I was promoted at every company I worked for, leading projects and leading people . I just never wanted to trade the hands-on work for the office with the view. More than two decades of writing software and I am still here, building. The tools changed completely, the industry changes fashion every six months, and I should be exhausted or bored. But I am not. It is not a lack of ambition. It is knowing exactly where I want to be. I tried to put into words why, because I think the answer says something about the work itself.
The part that never got old
There is a moment that still moves me, the same way it did when I was an intern writing my first real software. It is when a loose, half-blurry idea turns into something real that someone uses. You start with a confusing conversation and a badly drawn problem, and at the end there is something that did not exist before and that makes someone’s day easier. That jump, from nothing to something that works, never lost its magic for me. After so many projects, I still feel that little bit of wonder when the thing comes alive.
I never finish learning, and that is what keeps me
Software has a cruel and wonderful quality. You never truly master it. Every problem is a little different from the last one. Every time I think I have seen it all, a new context shows up, a new constraint, a new technology that forces me to be a beginner again. A lot of people hate that. For me it is oxygen. I like being a beginner. It is the only way to stay interested. I have reinvented what I know more times than I can count, and every wave, from my first static website to the AI that now writes code beside me, gave me something new to discover instead of something to fear.
The people, always the people
If I am honest, the technical part is only half of it. The other half is the people. There is an instant, when a team is stuck on a problem and suddenly gets unstuck together, that is almost physical, it feels that good. I felt it in my own company, a few of us crammed into one room, and I feel it even today on large, distributed teams. And there is the quieter side, watching someone I helped grow, and one day being taught something by them. That shows up on no dashboard, but it is one of the things I am most proud of.
When what I built actually matters
I never loved code for its own sake. I always loved code that makes a difference. Watching a business number move, watching a real person do in ten seconds what used to take ten minutes, knowing that the thing I built pays for itself. And it is not only numbers. I also love taking a confusing screen and redesigning it until the experience feels light, arranging the information on the interface until the person stops getting lost, turning a flow that made people angry into one so natural that nobody even notices it. Good information architecture is invisible when it works, and watching someone use, without effort, what used to be a struggle still gives me a pleasure that does not fade.
It is not always love, and that is fine
I do not want to make it sound perfect. There are bad days. The 2 am incident, the week when nothing compiles, the decision I made with full confidence that turned out wrong. Loving the work does not mean thinking it is easy. It means thinking it is worth it even when it is hard. And for me, it always has been.
After all of it
Two decades, two countries, a pile of technologies that do not even exist anymore, and I still open the IDE AI tool in the morning with curiosity. I think that is what I wanted to say. The work changed everything around it, the whole time, but the core stayed the same. Turn an idea into something real, next to good people, to solve a real problem. As long as that part exists (and my health allows), I am still here, happy to be a beginner one more time.
Pax et bonum.