Why I Still Love Software Development After 20 Years

When I first started in software development, I felt like a kid given a handful of Legos and very explicit instructions on what to build. I couldn't tell what I was building, but I could do the basic work.

As I grew into my role, I was trusted with more Legos—and more complex instructions. I learned how the pieces snapped together and connected to other parts of the build, where they were strong and where they were weak. Eventually, as a tech lead, I got to see the whole instruction book. I finally understood what we were building—and why.

But that wasn’t enough.

I didn’t want to just follow the plan. I wanted to design the build. I wanted to solve the puzzle, choose the pieces, and create something that worked, scaled, and lasted. I wanted to write the instruction book.

That’s what software development has always been for me: part engineering, part artistry, part puzzle.

Even now—20 years in—I still get a thrill from a clean implementation, a well-placed abstraction, or a refactor that makes the whole thing sing. The tools change. Languages evolve. But the joy of building never goes away.

If you’re just getting started: welcome. You’re going to love it here.