"Over a thousand developers contribute code to any given Linux kernel release. It's a process that works well from a technical perspective, but it's also one that has its fair share of shortcomings. In a panel at the Linux Foundation Collaboration summit this week, top Linux kernel developers detailed their common pet peeves about the Linux development model. It's a model that is not for the feint of heart ."

The false equivalence(s) put forth, which were triggered, I assume, by the thin skin involved... prove my point in a hilarious fashion.

Thanks.

Here is a hint: if you know what you are doing. Chances are you can understand whether criticism is due, and thus you can learn from it, or you can ignore it if its nothing more than a passive aggressive call for attention from someone at the other end of another computer far far away.

Yes, some people are assholes. But that is a general human constant regardless of whether one is involved in a open source project or not.

The false equivalence(s) put forth, which were triggered, I assume, by the thin skin involved... prove my point in a hilarious fashion.

Thanks.

I actually said it was utter bullshit not because I have a thin skin because it was the most appropriate comment.

You were just pigeon holeing everyone into one little box and claiming that everyone reacts the same to criticism.

Claiming they are false equivalences doesn't make them so.

You were claiming that those who do how to do something will just shrug off those berate them.

I gave two examples where different personality traits had very different outcomes, even though their ability were equal to their competitors.

You had no counter argument and called it a false equivalences and then declared yourself correct

:yawn: I suppose this is OSNEWS.

Here is a hint: if you know what you are doing. Chances are you can understand whether criticism is due, and thus you can learn from it, or you can ignore it if its nothing more than a passive aggressive call for attention from someone at the other end of another computer far far away.

Actually not always. I have found while working those that are most confident about their abilities are usually the worst, usually because it turns into ignorance and lack of an inner voice.

As I said upsetting people doesn't get you anywhere. Ulrich Drepper is a well known arsehole that looked after glibc, he was such an arsehole they basically forked it.

He held back GNU C library because he didn't want to listen to anyone except for himself and acted like an arsehole.

I have worked with people like him and they generally didn't last very long under employment.

Because you are working on an Open Source project doesn't mean you get a free ticket act like an arsehole.

Yes, some people are assholes. But that is a general human constant regardless of whether one is involved in a open source project or not.

Actually I work with many other develpers and while I think that some of them aren't up to scratch it isn't my problem ... I am not their manager.

However when something is going wrong I tend to politely ask them to do it the right way. If they continue doing it in a way that is detrimental to a project, I will consult my boss and go through the official channels.

Outwards calling acting like an arsehole doesn't get you anyway ... and arguing back in an unprofessional way makes you a bigger arsehole and alienates those that would otherwise be on your side.

BTW: Unless you have holes with asses (they are similar to donkeys) in them ... the person is acting like an arsehole ;-)

No, he's right. I have a living example, my son. He borders on, or is genius (hasn't been tested) but because he fears ridicule he won't do ANYTHING until he's practiced it hidden in his room for … ever. It goes beyond physical things as well. It takes us forever to coax him to do anything. My daughter doesn't give a whit... she'll do something even if she does it poorly and doesn't much care what you think.

I'm more like her... I've been programming for 27 years now and I've seen and heard it all. My coding style hasn't changed too much in all that time, I think you sort of latch onto a personal style early on... but I've had people say I don't comment enough, I comment too much, my code's too verbose, my code's too obtuse... etc.

One thing I tend to do, and it might raise criticism, but I don't really care, is that I often choose algorithms or code statements that are more descriptive than efficient (unless of course the code in question really needs maximum efficiency) because I want my code to be self explanatory for the next person who has to work on it. I also do comment heavily (probably too heavily - but I enjoy leaving little comedic excerpts for people later on .

I don't know. I've worked on operating systems, real-time banking applications, warehouse distribution software and for the last decade or so, web apps... and I've seen people belittle other people for poor reasons. I think peer code review, with guidelines and in a professional environment, is better than some public forum where people don't seem to know how to be constructive, only insulting.

To be honest, I think the distribution between skilled people with thick skin and without is probably about 50/50. However, people who think they're better than they actually are usually have very thin skin.