Being Ok With Deploying Shitty Code
February 01, 2019 • ☕️ 1 min read
So, at some point in your career as a software developer, you're going to run into a moment of:
Shit, deploy or keep tweaking?. Don't panic, it's a normal reaction and a cross roads we all come to eventually.
If you think of yourself as a good developer, you probably spend a lot of time trying to improve the quality of your own code. Even if you dont think you're a particulary good developer, I bet you still spend a lot of time trying to write the best code.
- You spend time reading best practices from your developer heros - Looking at you Jussi Hallila.
- You refactor your old awful code time and time again.
- You curl up in the corner and cry yourself stupid after trying to remove all the
ifstatements from your latest pet project.
And so, we spend a lot of time and energy trying to perfect our own craft, writing code that other people will awe at but how does this type of idealism stack up in the real world against business requirements?
In my experience, theres a bit of a disconnect between what developers feel they need to deliver and what we actually need to deliver.
Sometimes we like to feel smart, sometimes we want to prove we know what we're doing, sometimes we need to push ourseleves. None of these motivations however relate at all to buisness value delivered.
When we write code, the end goal should always be to deliver the most amount of value to the person at the other end of our program. Or in other words, your value as a developer shouldnt be measured in the quality of your code but rather the quality of the application you deliver to your user.
Personal blog by David O'Regan. I explain things with words and code.