"The company" is doing a lot of heavy lifting here. Conscientious individual contributors with little context will certainly make decisions similar to someone who feels ownership. If they knew as much as "the business," likely they would agree on the rationale.
Unfortunately, what happens is someone is seen as causing trouble more often, or complaining of this and that, receiving little correction, mentorship, or a quiet aside, and that path leads to ruin all the same.
The best compromise is to pick the battles, don't try to change the inevitable, and generally try and get along with folks. It's not the happiest circumstance, but practical and maybe something with more longevity than repeatedly dying on various hills.
"It's not your code" is a sense of freedom, but it ought to be accompanied by the engineer's duty to merely "observe and report," not to reverse or influence decisionmaking.
"The company" is doing a lot of heavy lifting here. Conscientious individual contributors with little context will certainly make decisions similar to someone who feels ownership. If they knew as much as "the business," likely they would agree on the rationale.
Unfortunately, what happens is someone is seen as causing trouble more often, or complaining of this and that, receiving little correction, mentorship, or a quiet aside, and that path leads to ruin all the same.
The best compromise is to pick the battles, don't try to change the inevitable, and generally try and get along with folks. It's not the happiest circumstance, but practical and maybe something with more longevity than repeatedly dying on various hills.
"It's not your code" is a sense of freedom, but it ought to be accompanied by the engineer's duty to merely "observe and report," not to reverse or influence decisionmaking.
if the code is worse after a refactor u should not be refactoring XD