|
Linus had a reputation for doing this, back in the day. He took some time off a few years ago, and while he's still very strict on quality, his tone has changed. I've run a lot of dev teams, and I see two side to this. On the one side, the worse thing you can do is build an environment where folks are scared to raise new ideas, or think of new solutions, for fear of being publicly humiliated. At best, you will get teams that do very average work. At worse, you'll loose all your good people. On the other side, I've had devs who thought they were god's gift for code, and made everyone's life around them, a misery. e.g. one guy spent months failing to implement an API with the front end he was writing, but despite that, he'd comment on PR's "This code is shit and needs to be rewritten." Folks like that need to be part of, what we call in the UK, a frank and open conversation, which I had one to one. This particular dev refused to back down, and left without working his notice. Going somewhere where they would, in his view, thank him for his feedback. Good luck with that. They guy that replaced him had the API working inside of a week. tbf, the API was terrible, but that's a whole other story involving IBM and SaleForce... |