Unraveling the Mystery of Last Year’s Code

Photo by Emerson Peters on Unsplash

Some bugs come out of the blue, and then there are some that are definitely your fault.

I’ve noticed many of my bugs are clustered around the same time of year. I think that my work quality drops off a cliff around the same time each year, and I’ve just worked out when that is.

It’s bonus time. Let me explain.

Bonuses

After Christmas is a special time. January might be bleak and cold for some, but around these parts, it is bonus time. 

After performance reviews, you get rewarded for your year’s work. Life is good (so long as you aren’t getting fired) and the company guesses that you should feel motivated.

So how did this end up demotivating The Secret Developer to such an extent that their code became a code smell? It doesn’t seem possible.

Giving up

I accept that I might be the only one. Most days I think about my notice period and if I get fired today how long will I survive?

I also dream of leaving my job calculating the best time to leave. Our annual 5% bonus accounts for a year’s worth of effort so I think the best time to leave is the day after the reward — or as soon as possible afterwards.

So, after my bonus, I look hard for a new job. Last year I practically gave up on coding features and debugging.

How it works

I’m at a slow-paced corporation. I decided to do as little as possible and since I work from home this is easily possible without anyone noticing. 

This meant that I didn’t put much effort into writing new features. My work was bugged.

Leading to…

Pretty much a year of fixing my own bugs. I didn’t work for a couple of months and applied for new jobs but there wasn’t that much available. A bad move, and one year later I’m still at the same job.

What we can learn

It didn’t have to be this way. Here is how to avoid the situation that meant The Secret Developer delivered sub-par work.

Recognize the Impact of Motivation

Motivation impacts the quality of our work. If I feel my motivation waning like this again I’m going to take action or make sure I’m fired. I’ll need to try to speak to my boss, but they’re not exactly available so I guess I’ll find another one.

Continuous Improvement

Instead of just checking out I’m going to work to become a better developer. That means improving and taking on more challenges. I’m going to make the best of a bad job and do what I can to get better, no matter what others do.

The Ripple Effect of Poor Quality Work

What really matters is doing work well and avoiding shortcuts for short-term gains. Today’s shortcuts can become tomorrow’s long-term problems (and did). I’m going to strive to maintain high standards in my work and avoid the ghost of poor-quality work haunting me.

Reflection

Bonus time should not be an end at all. Next time I’m going to use it as a milestone for reflection and planning. Use the time to set goals for the year and improve and maintain or elevate the quality of my work. It’s the right thing to do and it will be the better thing for me too!

Conclusion

Unraveling the mystery of last year’s code has been more than just a trip down memory lane — it’s been a stark revelation. Like waking up from a bad dream, I’ve come to understand the ghosts of my own making. The annual cycle of motivation, followed by disillusionment post-bonus, has become a self-sabotaging tradition that haunted not just my codebase but also my professional integrity.

I need to break the cycle. Actions you take or fail to take have repercussions. I just need to remember this come bonus time again.