Skip to main content

My problem with trying to be perfect with software.

Falling behind deadlines stresses the shit out of me. It doesn’t help that you have a manager telling you repeatedly that delivering user stories late will affect release.
I try to pinpoint the reasons why sometimes I fall behind on deadlines and I came to the following conclusion. I have this serious issue where I am trying to be a perfectionist (even though my work is nowhere near perfect) and I can never decide how to best get things done. Lesson of the day here is ‘just get it done’.
The issue here is that every time I spent time on trying to find the best way possible to solve an issue another possible way comes up. My common sense in Software Engineering says that I should “just get it done” first and work on making it better later. Working on making it better could it include peer review or incorporating the ideas of others.
The key here is that you can never get the ideas of others if you don’t have something to show them first. People understand better when they look at something and they are asked for ideas to make it better vs being asked point blank “how should I get this done”. Firstly, if you ask someone “how should I get this done?” you will possibly get an idea that will be 360 degrees different than your own idea. However, if you first build something and then ask them for ideas on how you can make it better, you have already laid down the ground work. Your peers can now only build on top of it. In this case, it will be hard for someone to come up with a drastic change to your initial thought.
Let’s summarize – dear self, for the sake of your wellbeing, please try to come up with the “best solution possible” before you start doing “actual work”. Start building things up, test them, improve them, repeat. This will save you time, help you in meeting deadlines and minimize stress levels while at work.

Comments