3 ms·
1. A lot of developers are missing something in the brain that allows them to feel empathy. 2. Coding is all mental (don't tell that to your hands). So, when y
by JustSomeNobody 12y ago
1. A lot of developers are missing something in the brain that allows them to feel empathy.
2. Coding is all mental (don't tell that to your hands). So, when you question a developer's code, it's kinda personal. Some take this hard. Too hard. So they build up a defensive barrier.
3. Developers are treated as a commodity by people with business degrees. This feeds the notion that they need to be perceived as the best (or at least towards the top). If that means not letting a newb show them up, well, so be it.
- Kalium 12y agoIt should be remembered that feeling empathy is not the same as being controlled by empathy. Just because I feel empathy for a newbie's struggles does not mean I am going to push sub-standard code live so they can get that feeling of success. As the article notes, a ruthlessly critical attitude towards your own work is very important. I'd argue that it's one of the most important traits that helps an engineer develop. If we don't teach that, we will collectively become a community of warm, emotionally supportive, technically worthless people.
- JustSomeNobody 12y agoExactly true. One should not be controlled by empathy. Being empathetic allows one to choose one's words wisely. The goal is not to allow sub-standard code to pass. The goal is to correct and educate, but do it in a positive way. Empathy allows one to put oneself in another's shoes and ask, "How would I want my mentor to correct me?" Don't get me wrong, I am not advocating the "even losers get a trophy" mentality. But I've been in code reviews that have turned into blood baths. That's just not appropriate at all. Ever.
- Kalium 12y agoI've never been able to find a way to be warm/positive/supportive/encouraging/empathic while also impressing on someone that their screwup might have cost the company six+ figures. Or worse - in some contexts, consequences can be kinetic. Blood baths are not acceptable, but positivity is not always capable of effectively communicating consequences. Positivity works best when very little explaining of mistakes is required. Sometimes an empathetic explanation that something should be better will suffice. Sometimes you encounter "It works, it's fine", and something more than empathy is required.
- JustSomeNobody 12y agoIf code has gotten out into the wild and has cost a company six+ figures, that developer is _not_ the company's biggest problem and it's not all his/her fault.
- Kalium 12y agoYou'd be surprised. Some companies give individual devs a lot of autonomy. My point is that positivity and empathy works best when people already know they've screwed up. Otherwise, you have to explain how they erred, what the consequences were/are, and how to fix it. The first two are more difficult to do in a positive way.
- jnbiche 12y agoThis is a depressingly perceptive comment. Is there anyway to counter or discourage these tendencies in other coders, do you think? Normally, that would be management's job, or that of senior devs. But the former seem to encourage, or at least tolerate hypercritical responses, and the latter often actively engage in them.
- JustSomeNobody 12y agoGood question. I don't really know the answer. I worked at a company where the developers were very negative. Conversations just dripped with sarcasm. I think it's infectious. If the mentors are negative and overly critical, I think people become like them at some point, if only because that's the only way to communicate with them. I think you have to be self-aware and just know when it's time to exit.