And in your original post you said you knew how to solve the problem but wanting the dev to learn a lesson. SO you must regard training time more valuable than customers bugs.

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 caused extra downtime for the customer so you could make an example of someone and relish in your victory.

You're winning an argument while you lose the war.

Well, bugs will come back later if he does not updates his knowledge.

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.

This is what makes startups so special, and powerful.

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.

Let's imagine that lots of people don't like working with assholes. Let's also imagine that good developers can more reliably pick where they work. If that's so, being an asshole skews your hiring pool away from good workers. That might very well cost you money.