Live data from Hacker News

Brilliant Jerks in Engineering

brendangregg.com

241–243 of 243 posts

Re: Brilliant Jerks in Engineering

#241

Earlier quoted context omitted.

> people "lower down" in the hierarchy will also act like jerk It's not clear to me he is a jerk. If LT only shouts when things are important, people without important tasks have no reason to shout.

Important to whom?

Anyone who depends on, or is invested in, the security/stability of the Linux kernel, or cares about such a reputation. Which should include core devs.

Re: Brilliant Jerks in Engineering

#242
post #11

This is a great article. It's a terrific opportunity for introspection. I do however want to point out that some of these may be less about being an insufferably relentless jerk than other pieces. > He is late to meetings, ... then looks at his phone or laptop while ignoring everyone around him This is also a pretty common indicator for ADHD. Not to say that excuses being a "jerk", but there are people out there that…

You will know it is not due to ADHD if the first thing they say when you mention them being late in a meeting is 'I have ADHD'. Being late at meetings is one thing that happens to everybody. Being doing other stuff during meetings, stand-ups or what not, in a group setting, while having your legs up on the desk playing with your phone is being a jerk.

Re: Brilliant Jerks in Engineering

#243

Earlier quoted context omitted.

He’s essentially saying “this userland code is beyond stupid, but we don’t break userland so here’s how we can keep it working.” The comment is neither aimed at the contributor (who works on kernel code) nor the reporter (who did not write the code). In fact if you read the rest of the thread you can see them concur and joke about it.

Are the people joking about it equals or can Linus decide who gets fired?

Both. The reporter is an equal, and the contributor is a subordinate (in a sense).
Post reply on HN