[dgb23]

My mantra related to that is "be mean to the code and nice with to programmer".

In order to learn and make things better you _have to_ be critical. But the way things are communicated is very important so everyone is on board.

"We could do better here" - no matter who exactly was responsible in the past.

"This made sense at the time but with what we learned..." - remind each other that improvement and learning is part of the whole deal.

"I like the simple and expressive core idea of this, but if we expand this further..." - elevate and develop the good stuff that's already there.

I make jokes about my mistakes, bring them up early and often. Everything is a bit lighter and easier with a bit of humor and without the fear of making mistakes.

And vice versa it is just as detrimental to be afraid to bring mistakes and inadequacies up and criticize them. It's much more fun and productive if things are continuously improving.

[edgyquant]

This works great until you get an engineer who pushes back constantly claiming it’s a time trade off or that this code is correct and you just don’t understand it. Sometimes humor doesn’t cut it.

[plaguepilled]

I have worked with a few such "strong personalities" and while I agree they can be slow on receiving criticism, I disagree that one should therefore resign to more forceful communication.

There are many alternative avenues in a professional setting when presented with an opportunity to argue, even if you're being blocked by a superior.

The crucial thing to remember is you cannot ensure your "social workaround" will work, but you can always ensure you act professionally. Whether that impacts the sprint is a matter of circumstance, but mild, cheery professionalism always improves the workplace culture.

[Retric]

Yea, some people can be unbelievably toxic.