“Wow. Look at this code, it looks so nice! And it’s so clear and easy to read!” Clarity and readability are admirable things to aim for, but is it possible that the quest for “perfect” code is preventing you from actually RELEASING real functionality to the user?
I can’t solve this one, and I think I need your help. So, a developer was responding to a code review comment I made and they simply asked me, “why would I do that?” I gave my standard, dusty answer: “because you have to code defensively— you don’t know what the future holds.” But I suddenly realized… am I proliferating a fear of the future? How could I code fearfully when I run CubicleBuddha.com where I blog so often about living happily in the present? I’ll share the specific code example with you. I’m hoping to hear from the community whether my solution is “coding in the moment” or if I am actually bowing down to the fear.
We all have reasons for holding onto the past, like that Transformers lunchbox that I couldn’t handle throwing away. I loved it, but the truth is I was never going to use it again. But in the realm of professional software engineering, holding onto anything that isn’t being utilized can wreak havoc on a codebase through unintentional bugs and clutter that hurts maintainability and team moral. This unused code is called “dead code.” But how do we know when code is dead? And worse yet, how do we convince ourselves that it’s finally okay to let go of that lunchbox you’re not using anymore? The following tips will help you to get rid of the hoarding problem.
So, I’m looking out from my home office window about to start this blog thing. It’s gonna be an amazing opportunity to connect with people about what makes myself and them happier and healthier at work. Can’t wait!
Update: This was not supposed to be my first post– I made it just to test out the blog. So when I returned just now to upload what was supposed to be the “real” first post, I had a weird realization… isn’t being in the moment and forgiving yourself of the past what this blog is supposed to be all about? Yes. So this “temporary” first post is here to stay. As we’ll talk about very soon, being happy with your work means patting yourself on the back even when the outcome isn’t perfect. So come along and read how to grow (as I do) in learning to accept the past and embrace the happiness of the present.