3 ms·
The problem is when the manager gives out quick, direct harsh feedback, but the manager himself doesn't accept any from his reports. That is a very toxic enviro
by Jensson 5y ago
The problem is when the manager gives out quick, direct harsh feedback, but the manager himself doesn't accept any from his reports. That is a very toxic environment. So if you want to do this then you need to make sure that you yourself can handle it. If a report gives you harsh feedback, don't get angry and retaliate for no reason, that feedback is just a piece of information, instead just explain why you did what you did.
By the way, any programmer accepts direct feedback, otherwise you can't work with a compiler. Feedback should be direct, quick and fair. I see no reason to do anything else, and if someone feels uncomfortable with that you can just train them to get used to it, everyone who programs can get used to it quickly. However you can't train your manager to accept direct feedback as he will just fire you if he can't already handle it.
- barrenko 5y agoMy pet theory is this is why tech beat out basically every other industry in management and company culture. You work with an unforgiving compiler for a couple of years? You know something about feedback. (Personal favorite F#) Also final point, BS managers are dime a dozen. As a manager you should welcome getting feedback as it gets you to be like Juggernaut from Marvel.
- atoav 5y agoInteresting thought, I think IT people indeed deal with feedback differently.
- sideshowb 5y agoI'm not sure I buy this argument. Compiler feedback is 100% logical and deterministic. Human feedback, even when precise (which it often isn't) is still influenced by the whims of others. The programmer archetype finds the latter frustrating.
- watwut 5y ago> My pet theory is this is why tech beat out basically every other industry in management and company culture. I dunno, tech management always striked me as pretty bad.
- Verdex 5y agoI don't know. There's some brutally honest feedback that I would appreciate. Like, if my feedback was like Rust. Here's a list of the 6 things you did wrong, a helpful diagram for how to understand the failure, a few tips for improvement, and a link if you want to read more. On the other hand ... a lot of feedback feels more like ocaml. Something's wrong. It's probably on this line. Maybe. Does "int * int * int" mean anything to you? Look maybe go put some parens on some of your match statements or something. Good luck fixing it. Of the significant critical feedbacks that I've gotten (in tech) only one of them was like a Rust compiler feedback. The others were much more like working with ocaml. And pragmatically they didn't even seem to be valid (a lot of subjective-ness was involved, so I can't say they were objectively wrong ... but when followed bad things happened).