In response to This*: Stop letting engineers get away with social ineptitude

I can't agree. My professional experience involves enough interaction with extraordinarily talented engineers who have extremely abrasive personalities. Often, that abrasiveness is a side effect of their talent: the same ability which allows these talented men and women to see through the complexity and grasp the conceptually simple steps necessary to solve the problem also helps them see through the seemingly-meaningless boilerplate and social grease that we call people skills.<p>You can argue that if the culture shifted such that these individuals were marginalized and forced out then they would change out of necessity. I could see this argument--idealistic to the point of fallacy though it is--presented at other venues. However, those who frequent Hacker News should know that these people will find talented others who are capable of dealing with their social immaturity and will end up co-founding their own company and, unencumbered by the enforced social niceties of this fictional society, may very well end up becoming a dominant player and returning to the status quo.

I don't think the issue is one of social incapability, but one of failing to match a hire with his responsibilities. If you're going to have your technical guy interacting with customers, then being technically brilliant but lacking customer service skills is not a good fit.<p>I work for MegaCorp. We have developers here that are incredibly difficult to get along with and a few that are great. There seems to be this sense that the more capable and intelligent a person is the more frequently they're jerks to deal with. I haven't found this to be true. There are plenty of good devs that aren't "holier than thou" (and one of the best devs I worked with was clearly on the extroverted side, though most of them land on the introverted side of things).<p>I will say, though, that more people have ended up being let go for attitude, rather than work quality where I am employed. To put it plainly, in a large corporation where you have to work amongst imaginary and real bureaucracy, it doesn't matter how skilled you are, if you can't work with people you won't get anything done. Your fantastic project/work will not be looked at because nobody will care to see it and your manager (often non-technical) won't want to show it off because you keep aggravating him or putting him in the awkward position of defending your behavior to his superiors.

I think the 2 "skills" in question here are "tact and maturity".<p>No one is asking engineers to be salesmen or glad-handing PR people. But as so many others have pointed out, any mature adult, no matter their vocation, should have the basic social understanding of "this is ok to do/say" and "this is not ok to do/say" for most given situations.<p>i.e. tact..<p>And to all of you who hide behind the "that's not learnable for me, I'm awkward/nerdy/shy/neckbearded" excuses, I call bullshit. Grow up.<p>I was the epitome of awkward, shy and socially inept (since childhood) as a developer, and in my mid-20s I made the conscious choice to overcome these things. To become more professional and to learn how to communicate and interact properly with my co-workers, superiors, reports and YES even customers.<p>And I did it by just throwing myself in the fire. It was hard at first, but I figured it out. And it has opened so many doors and opportunities for me.<p>The combination of my technical competency as a developer and my professional communication skills has been a huge asset for me when looking for work and new opportunities.<p>Plus, on the lighter side, it eventually helped me with my inter-personal communication and social skills as an added bonus! (i.e. it got me laid more) :-)

&#62; yet employers often find that people filling these roles with poor people skills are still employable. This needs to stop. I’m of the opinion that every position is customer-facing.<p>Well fuck me, then. I'm sorry, it's already hard enough for me to find jobs as it is.<p>Frankly I'm glad we live in a society that has a place for us social retards. I really do believe that social "skills" can't be learned, at least not well. I'm glad there's a place for us, just like I'm glad there's a place for people who are short, black, or ugly. Yeah, there are fewer employment opportunities, and our salaries are handicapped consequentially (tech skills + people skills = high payed manager!) but telling us we should be out on our asses for something we can't help is cruel.<p>Obviously the guy should have been fired though.

Wrong problem. This whole issue was just typical assholery, it's not a failure of introverts or antisocial behavior. By all means, stop hiring assholes, but don't blame it on people who just hate smalltalk and never bothered to learn.

This guy is mistaking "poor people skills" with "being an asshole". I'm not sure whether the two are so clearly related : there are a few different manifestations of lack of social skills, and there are jerks who don't have much social skills issues.<p>"All it takes for someone to be good at customer service is: [...]".<p>This sounds so simple. And it misses quite the point. Lacking "social skills", is precisely this : not knowing how to behave completely "normally" (whatever that means) with other people. Like, not grasping the effect of your words, or not being able to think them through fast enough before saying them. Of course, I want to be helpful, and to answer the person in front of me (or on the phone). That doesn't mean that it is what the person will see or hear.

There seems to be a convention amongst the techie crowd that social rules are a silly bit of nonsense that dumber people engage in. This is not at all the case.<p>When I handle a project from beginning to end, it goes smoother. I find any mistakes I've made myself; I know what assumptions I made at every step; I don't have to get my head around the job over and over again; it's all-round easier.<p>When a team does projects, it requires rules, with some rigidity. Each person has to act somewhat like an object-oriented sub-routine, with guaranteed input, guaranteed output. This does add some overhead, but it allows each person to function with relative freedom in his own space.<p>Social rules and conventions are the rules for the team comprised of a culture doing the project of living. They allow us to get through the day using hundreds of social shortcuts; assumptions about each other's behavior, needs, wants, expectations.

wait, what? There is a difference between being socially inept and destroying data because you think someone is a jerk. This difference is similar, I think, to the difference between honking or flipping someone off in traffic and, say, ramming them.<p>I mean, one of those things is just being rude. The other is going out of your way to damage someone else.<p>Personally, I would put up with a lot of the first. Rude people, of course, shouldn't be in customer service, but on the back end, eh, if they are good enough, I think they are worth keeping around. Especially if they are the extremely direct, blunt and honest kind of rude, I think they can actually be better back end people, sometimes, than people who try to twist things to look better than they are.<p>But people who destroy things when they are angry or insulted? yeah, those people should not be let anywhere near a root prompt.

I believe that what many are quick to refer to as <i>social ineptitude</i> is a keener sense of bullshit detection, combined with the inability to take it with a smile.<p>Imo, most <i>socially-inept</i> tech people are simply individuals that are more sensitive to the hypocrisy and nonsense one is exposed to when dealing with the public.<p>I don't know if being a tech person is a cause or an effect of that bullshit sensitivity, but as a programmer who used to be a bouncer in a bar a few years ago, I can tell you that some of my non-tech colleagues were by far very quick at losing their temper than I was.<p>Now, there's a difference between being bullshit intolerant and being malicious. I am of the firm opinion that the actions of that Tech support guy (deleting data out of pure spite) are certainly not characteristic of the tech-guy stereotype as we know it.

Good engineers' poor personal skill is often a manifestation of traits that allow them to be good engineers in the first place (though not a necessary condition). The same way Steve Jobs and James Cameron are horrible bosses to work for, the same way CEOs often suffer from ADD and bi-polar disorder, and the same way so many amazing Nobel Laureate have autism problems. If you appear ordinary in your personalities and traits, then chances are that you aren't the outstanding leader of your field.

500 - Internal Server Error<p>Stop letting writers get away with technical ineptitude!

That's not social ineptitude. That's malicious behavior and destruction of property. There is a difference. Please don't conflate the two.

What's so hard about kindness that engineers can't figure out? I really don't buy that excuse.

Based on some digging around I have a very strong suspicion that Jules is the founder and only employee of This*. I think the "new employee" will likely just be a new email account with a different name.

"The understanding that they represent their employer and that people are relying on them" - Most developers have huge, inflated egos.<p>"A compassionate, helpful, and courteous attitude" - See above.<p>"The knowledge of whatever their supporting" - An understanding of the technical side of a product is vastly different from the functional side as its easy for a developer to say "This is sample. You hit X, then Y then select Z and find Q" which does not translate in any way to a client understanding a product and the frustration of dealing with "simpletons" shines through - thus leading to outbursts like we've seen.<p>This is of course the standard. I would imagine entrepreneurs and such do not follow this guideline, but for a generic programmer these traits are not something that are a typical side-effect of the craft unless you start moving up in rank.<p>The fact that the author would be offended by the statements mentioned really reiterates the point that most developers take things entirely too personally. I know I did for the better part of 10 years.

I know a few universities that are pushing programs to "fix" this problem in engineers by encouraging them to do more presentations and group projects.<p>It seems like there will always parts of "geek culture" that just don't care. Perhaps they're even proud of social ineptitude? But those aren't engineers I would want to work with.

Offence: Engineer is offended by customer and flushes the customers livelihood (website)<p>Cure: Management should be offended by engineers and flush THEIR livelihood (job)<p>Seems symmetrical, but perhaps over-simplifying the problem? Of course I realize that the article above doesn't directly advocate firing the engineer, but many high-functioning technical people just cannot realistically be trained to be social animals too. Those abrasive nerds are really productive outside of a customer service role, so wouldn't a better solution be to fix the mis-allocation of tech staffing resources to customer facing roles?<p>edit: and yeah, maybe the problem is that this particular engineer was just a dick, and we shouldn't use him as an example in the discussion of technical vs social roles in our companies.

Yeah, I don't believe for a second that this is a trait that belongs exclusively to engineers.<p>Here's a thought: anyone in a position of "power" is susceptible to this dynamic; if "social" relationships were described as an equation, then power (P) would be inversely proportional to the effort or energy (E) you need to expend to maintain any given social relationship (R),<p>P = R/E<p>The more power/authority you wield, the more of a jerk you <i>can</i> be (not should be or are), because the value of the relationship is lopsided - you don't <i>need</i> to spend as much energy on it.<p>The power an engineer holds is that they are often quite valuable within an organization, and tend to have an easily transferable skill set.

I'd put the blame on whoever hired the guy and put him out front as the customer support guy, without monitoring him. Some of it's attributable to the support guy, but most of the blame should fall on his bosses.

I think the author needs to display a little bit of that compassion he's talking about and realize that learning social skills is not as easy for everyone as it might have been for him. The world is full of different kinds of people, and it takes all kinds to run a company. If Jules is truly great at the technical side of his job, I see no problem with freeing him to get on with it.

I don't believe this is something special to engineers. Hey, back home, in "less civilized" part of the world, you can be beaten up by waiters if you are complaining (being asshole) about meals at a restaurant.<p>In order words, "tact" is something you need to learn. Especially in internet world where doing something stupid is just a click away.

The last line of the article really just sums it up for me. If you don't have basic every day people skills, you'd better be <i>damn</i> good at what you do, otherwise, it's probably not worth it as you alienate your coworkers and make life difficult for those around you.<p>And that's <i>before</i> you get a customer-facing role.

The vast majority of web hosting shops are not "companies" with "employees" and "management." They are one or a few guys with some dedicated servers and most tier-1 support outsourced to huge web hosting support shops.<p>This seems like a whole lot of attention over what seems like one guy who is an asshole.

Web hosting tech-support people are NOT "Engineers". Or for that matter tech.

I kinda wish there were ways to add URLs to an extant thread rather than starting new threads with URLs. Because, for fuck's sake, this is like the fourth link on this boring topic.

500 - Internal Server Error.<p>Can anyone post up a copy? Seems like a sensational title - would love to see the argument.

<i>500 - Internal Server Error</i><p>Someone needs a socially inept engineer to fix their website.

I think one problem here is that they non-chalantly made "poor people skills" equal to "abusive behavior towards costumers" and used the "awesome tech with poor people skills" image as a euphemism in their PR to comb over a VERY ugly situation where they were getting a shit storm of bad PR - it was probably the only way out of that situation short of publishing "welp, sorry, he was a total jerk-off asshole and we fired him".<p>I do think the (stereo-)typical techs can be said to prefer focusing on interesting problems and on their computers rather than having to deal with people all day long - possibly angry or even downright abusive customers demanding support. I don't see the (stereo-)typical techs as slimy and very skilled at playing the political game and manipulating people and advancing the career ladder through it. (which is something I would see as very specific but definitely STRONG people skills, no matter how repulsive.)<p>But that doesn't mean all techs don't have any manners or empathy.

"As a technical person who has worked many customer-facing support roles"<p>Stopped reading right there.<p>"I am a technical person who also has ability Y, therefore all technical people should have ability Y."<p>This is the thinking that would sit Magic Johnson down and say "Your ball game is pretty good, but your golf game is awful. Stop working on your basketball skills and start golf training."<p>Bottom line: customer support requires ability, certain personality traits, and training. Do not let <i>anyone</i> (technical, non-technical, CFO, anyone) handle customer support if they are not qualified. It will end badly.

As soon as people stop letting non-engineers get away with total, utter technical incompetence and stupidity.

I suppose some of it is attributable to Asperger's -- some of it. In many cases, though, I can't help but suspect laziness and a holier-than-thou attitude.

I think he's reading too much into it. I have seen waitresses get moody and piss off customers, MBAs that have had violent disagreements and stomped out or quit on the spot. A Tmobile once hung up on me when I complained loudly about not getting cell service and being stuck in the office unable to call a cab.<p>There are tons of geeks who are really personable.<p>Taking one example of an engineer who may have had a bad day because of people being rude/confrontational and extrapolating them to social ineptitude of engineers is missing the forest for the trees.

I clicked on the link and got a "500 Server Error". I cal that pretty damned rude and socially inept.