It’s a rarity because the nano second a prototype works, it never gets touched again because management only heard it works and don’t give dev more times to make it proper.
So imagine management deciding to ask devs to go back and clean-up a codebase, pure fantasy.
Wish granted. Now management questions why everything “takes you so long”, and you were passed up for promotion in order to promote Jim (just last week, he did a presentation about his new feature that uses fancyassDB).
Don’t worry, though. They’ll need your help soon, in order to make Jim’s fancyAssDB pet project sync with the oldAssDB legacy stack (which is a completely different stack. Have fun extending all of Jim’s hardcoded features). He quit the company to join a crypto startup. Still no promotion though, since you finish stuff kinda slow (I mean, Jim built it in 2 weeks, so it can’t be too complicated).
Nope. It’s the norm. Well maintained code is a rarity.
It’s a rarity because the nano second a prototype works, it never gets touched again because management only heard it works and don’t give dev more times to make it proper.
So imagine management deciding to ask devs to go back and clean-up a codebase, pure fantasy.
So just don’t tell “management” it’s done. Easy.
Wish granted. Now management questions why everything “takes you so long”, and you were passed up for promotion in order to promote Jim (just last week, he did a presentation about his new feature that uses fancyassDB).
Don’t worry, though. They’ll need your help soon, in order to make Jim’s fancyAssDB pet project sync with the oldAssDB legacy stack (which is a completely different stack. Have fun extending all of Jim’s hardcoded features). He quit the company to join a crypto startup. Still no promotion though, since you finish stuff kinda slow (I mean, Jim built it in 2 weeks, so it can’t be too complicated).
I try to do that as much as possible, but comes a point where you can’t push back the task in the next sprint.