Sometimes it is all about technical details, costing, pricing efficiency and getting things done.
Because at the end, it is all about the money. And defects are expensive.
And you may prefer an efficient worker with bad attitude than a cool bro that introduces bugs in code like a priest in a brothel.
Because bugs cost more money than assholish workers.
AND now you start arguments with anyone that disagrees with you??
Take a chill pill, fix the bug, move on, laugh a little, and look the poor bloke in the eye and say you are sorry. People will respect you more, and maybe next time things won't get so blown out of proportion. Above all, relax, you got this bro :-)
You're winning an argument while you lose the war.
But, yes I was thinking the same myself. Whatever, I lost the war.
In fact, I prefer a boring life with less bugs on the long term and a bad reputation. But, it does not seems like a wise choice given the reactions.
I fully acknowledge my inadaptation to the actual era.
I think, I prefer to focus on the agenda of tomorrow and the tasks that must be done. You are right, customers come first.
There are battles that are not worth to be fought after all.
Well, tomorrow is another day. Thanks you all.
Everybody now knows (or should know) that the more modern type of developer environment - wear what you want, arrive when you want, stay home when you want, have all the free coffee you want - makes them MORE productive.
Pissing them off or giving them a shitty environment to work in makes them less productive.
And productivity = money.
Of course defects cost money. One defect means you lose money once.
Less productivity means you lose money every single day.