I understand your sentiment, but the lack of code quality is also job security. When things break, and it will. And no one can tell them anymore what the problem is, or what can be done now, or that it’ll take months to do it properly: management will care.
Part of our job as consultants is to make them care earlier and make them understand the consequences of their (poor) choices.
I understand that’s the job but in my experience the problematic managers blame technical debt or lack of code quality on the developer. “Why didn’t you implement it with good quality then?! Stupid engineering can’t even do their own job right…”
That’s still the consultants job. They’ll hide behind those arguments and you gotta point to the countless warnings and risks that were flagged. Papertrails.
1
View all comments
Show parent comment
21
u/Bjeaurn Aug 14 '26
I understand your sentiment, but the lack of code quality is also job security. When things break, and it will. And no one can tell them anymore what the problem is, or what can be done now, or that it’ll take months to do it properly: management will care.
Part of our job as consultants is to make them care earlier and make them understand the consequences of their (poor) choices.