[Clubber]

It depends if you want "yes" men, or people to disagree with you. It might sting sometimes, but people who are willing to argue with you are much more beneficial to the organization for the most part. (I accept that some people just like to argue for the sake of personal satisfaction, I'm assuming this isn't the case here).

Remember, they aren't making widgets, they are engineering software; it's a high knowledge, high skill task.

[ygaf]

>It might sting sometimes, but people who are willing to argue with you are much more beneficial to the organization for the most part.

>The thing about shit code is it costs 2x, 10x, 100x of technical debt later.

I'm on board with all those things, but bear in mind the insubordinate guy is alleged to just think it's 'bloat', not that he thought it would undermine the whole architecture of the code (and it's easy to imagine 1 additional class variable not doing so). Bloat is often a problem of autists.

[Clubber]

Yes, that's a good point. The facts are scarce and it's hard to tell what's going on, so I can only make assumptions. I'm making assumptions based on my experience. If I bother to speak up about something, I think it's worth talking up about. Could it be the guy was just being a prick? Absolutely.

[abiox]

> It depends if you want "yes" men, or people to disagree with you.

having an opinion and outright insubordination are two entirely different things. the former is fine, while the latter is toxic and destructive.

> Remember, they aren't making widgets, they are engineering software; it's a high knowledge, high skill task.

honestly, this mostly applies to areas that have advanced requirements. a lot of programming is not particularly "high knowledge, high skill", from business process stuff to web development.