Not Precious About Code

I used to be precious about my code ever since I learnt programming. Every line was carefully crafted, every function meticulously designed. But over time, I’ve changed my approach. Being overly attached to code isn’t practical in the long run.

These days, I prioritise getting things done. If my code works, it’s ready to go. Is it perfect? Probably not. Does it solve the problem? Absolutely. Can I refactor it later? For sure. I’ve learnt to focus on functionality over perfection. In the real world, working code is more valuable than theoretically perfect code, or no code at all.

Pragmatism has become a key part of my approach. There’ll always be more than one way to solve a problem. No need to reinvent the wheel. I used to spend loads of time on browsing code libraries for hours and finding the latest hot framework for my project. Now, I go straight for what works. It might not be the most elegant solution, but if it gets the job done efficiently, I consider it a success.

These days I really celebrate the “good enough” mindset. Striving for perfection often hinders progress. I’d rather have code that’s sufficient and actively solves problems than code that’s theoretically perfect but not in use.

I’ve come to realise that, while it’s far from perfect, PHP is where I feel most at home. My journey in web development actually kicked off with PHP4 back in the day. Sometime in 2004, I learnt PHP out of necessity — I wanted to tinker with some bulletin board software and eventually ended up releasing plugins for it and became deeply involved in the community.

Sure, I could sit down and master Ruby, Node, or Python. But even now, PHP is what flows from my fingertips without friction. This isn’t about PHP being the best language out there. It’s about recognising where your strengths lie and leveraging them. While it’s great to expand your skillset, there’s also value in honing the tools you’re already proficient with. For me, that’s PHP.

If you’re still treating your code like a delicate work of art or constantly chase the latest shiny framework, it’s time for a rethink. Your code isn’t a museum piece; it’s a living, breathing tool. Embrace imperfection, focus on solving problems, and let your code evolve. Trust me, both you and your work will be better off for it.