Why I Code and Why It Matters to Understand What You Write

Reference

Coding has become more than just something I do for a living—it's a part of who I am. But it wasn’t always this way. When I started, it was about getting the job done, meeting deadlines, and solving problems as quickly as possible. Yet over time, I learned something deeper: understanding the code you write is just as important as writing it.

It’s like a mechanic who doesn’t just fix a car but understands how every part fits together, or a doctor who knows exactly how each drug will affect the body. If you don’t really understand the code you’re putting into production, you’re just piecing things together without knowing how they’ll hold up. You might get something that works, but how stable is it? How efficient? What happens when something goes wrong?

If you’re blindly copying code from Stack Overflow or following tutorials without digging deeper, you're setting yourself up for frustration later. Technical debt piles up, bugs creep in, and maintaining that code becomes a nightmare. Worse, you risk losing the respect for what you're creating.

And that’s where the shift happens—when you start to care. You stop seeing code as just lines to push out and start seeing it as a craft. That’s when you grow. Every time you dig deeper into why something works (or doesn’t), you improve. You build confidence and can start making better decisions. You begin to recognize patterns, catch bugs earlier, and solve problems more effectively.

But this isn't to say you have to understand everything from day one. You don’t need to know the physics behind an engine to drive a car. Similarly, you can code without fully grasping every single concept. However, the more you learn and challenge yourself, the more those pieces fall into place. You start with the basics, then expand your understanding until you're not just coding—you’re creating.

For me, coding has shifted from something I had to do to something I want to do. It became therapeutic, a space where I can get lost in the problem-solving and emerge with something that works because I took the time to understand it. It’s not always easy, and there are days when I feel stuck or frustrated. But that’s part of the process, and it makes the moments of clarity, when everything clicks, even more rewarding.

I’ve found a sense of fulfillment in coding that goes beyond just writing functional code. It’s the joy of mastering something difficult, of feeling like I’m growing each time I open up a new project. Coding has become more than a career—it’s a passion.

So, why should you take the time to really understand what you’re writing? Because it’s how you go from being a code monkey to being a craftsman. It’s how you take pride in your work, how you reduce errors, and how you enjoy the process. You don’t have to be perfect, but if you care about the details and keep learning, you’ll eventually reach a point where coding is not just a job—it’s something you love.

And that’s when it gets really fun.