![](\"http:\/\/www.developer-tech.com\/media\/img\/news\/xlinus_torvalds_linux_code_review_empathy.jpg.800x600_q96.png.pagespeed.ic.1klZkyxsq3.jpg\")
<\/p>\n<\/p>\n
Following a promise to address his unempathetic approach<\/a> towards kernel developers, Torvalds already seems to be more considerate in code reviews.<\/p>\n Linux creator Linus Torvalds recently acknowledged his problems in an email to kernel developers in September.<\/p>\n In his email, Torvalds wrote:<\/p>\n \u201cI am not an emotionally empathetic kind of person and that probably doesn’t come as a big surprise to anybody. Least of all me. The fact that I then misread people and don’t realize (for years) how badly I’ve judged a situation and contributed to an unprofessional environment is not good.<\/em><\/p>\n This week people in our community confronted me about my lifetime of not understanding emotions. My flippant attacks in emails have been both unprofessional and uncalled for. Especially at times when I made it personal.\u201d<\/em><\/p>\n He ended the email saying he would be taking some time off to get assistance on understanding people\u2019s emotions and how to respond appropriately.<\/p>\n Torvalds promised the email wasn\u2019t him wanting to walk away from Linux development and that he ‘very much’ wants to continue working on it as he has for almost three decades.<\/p>\n Last week, Torvalds showed off his more empathetic approach in an issue with the HID pull request and its introduction of the BigBen game controller driver that was introduced. In particular, that it was enabled by default.<\/p>\n This was his response:<\/p>\n \u201cWe do *not* enable new random drivers by default. And we most *definitely* don’t do it when they are odd-ball ones that most people have never heard of.<\/em><\/p>\n Yet the new ‘BigBen Interactive’ driver that was added this merge window did exactly that.<\/em><\/p>\n Just don’t do it.<\/em><\/p>\n Yes, yes, every developer always thinks that _their_ driver is so special and so magically important that it should be enabled by default. But no. When we have thousands of drivers, we don’t randomly pick one new driver to be enabled by default just because some developer thinks it is special. It’s not.<\/em><\/p>\n So the default !EXPERT was completely wrong in commit 256a90ed9e46 (“HID: hid-bigbenff: driver for BigBen Interactive PS3OFMINIPAD gamepad”).<\/em><\/p>\n Please don’t do things like this.<\/em><\/p>\n Linus\u201d<\/em><\/p>\n The response is firm but fair. It doesn\u2019t come across demeaning or aggressive towards the developer, just sets them on the right course.<\/p>\n A response to a similar issue last November invoked the following response from Torvalds:<\/p>\n \u201cYou add new drivers and then default them to \u2018on\u2019.<\/em><\/p>\n THAT IS COMPLETELY UNACCEPTABLE.<\/em><\/p>\n I don’t know why I have to say this every single merge window, but let’s do it one more time:<\/em><\/p>\n As a developer, you think _your_ driver or feature is the most important thing ever, and you have the hardware.<\/em><\/p>\n AND ALMOST NOBODY ELSE CARES.<\/em><\/p>\n Read it and weep. Unless your hardware is completely ubiquitous, it damn well should not default to being defaulted everybody <\/em>elses<\/em> config.<\/em><\/p>\n But something like CONFIG_DELL_SMBIOS sure as hell does not merit being default on. Not even if you have enabled WMI.<\/em><\/p>\n EVERY SINGLE “default” line that got added by this branch was wrong.<\/em><\/p>\n Stop doing this. It’s a serious violation of peoples expectations. When I do \u2018make <\/em>oldconfig<\/em>\u2019, I don’t want some new random hardware support.\u201d<\/em><\/p>\n So far, it seems Linus\u2019 time off (which is well earned) has done his people skills a world of good. There\u2019s less of his profanity-ridden messages and general lack of professionalism when it comes to communicating with developers.<\/p>\n For most of us, it\u2019s good to see. For Linux kernel developers, it\u2019s well overdue.<\/p>\n