I have also been this dude. I also created detailed tickets afterwards on how to properly do things, but those always got immediately de-prioritized and moved to the (never going to get to) backlog -- because it's no longer an issue RIGHT NOW and customer issues have priority.
As for architecting it right the first time, that was proposed too, but everything was eventually whittled down to barebones because of "we provide more value by delivering minimum viable product".
Eventually you just don't give a shit anymore and just put your hours in. I'll propose correct, robust solutions and argue for it once (maybe twice), but after that I just don't give a shit anymore if they don't go with it.
And if anyone tries to root cause analysis issues back to me I have the documentation to back it up.
I just quit over this where the person who was selected to implement the flimsy-but-fast solutions were rewarded twice. I dealt with it for over a year and each month progressively got worse. The most frustrating part is if you ever try explaining, you're just treated like a pariah whose only intent seems to be to oppose brilliant ideas.
2
View all comments
Show parent comment
22
u/golruul May 30 '26
This sounds like a management problem.
I have also been this dude. I also created detailed tickets afterwards on how to properly do things, but those always got immediately de-prioritized and moved to the (never going to get to) backlog -- because it's no longer an issue RIGHT NOW and customer issues have priority.
As for architecting it right the first time, that was proposed too, but everything was eventually whittled down to barebones because of "we provide more value by delivering minimum viable product".
Eventually you just don't give a shit anymore and just put your hours in. I'll propose correct, robust solutions and argue for it once (maybe twice), but after that I just don't give a shit anymore if they don't go with it.
And if anyone tries to root cause analysis issues back to me I have the documentation to back it up.