4 ms·
A part of the hacker mindset ("hacker" as used in the jargon file, and in this site's title) is intolerance of stupidity. Ignorance is one thing, that can be le
by Karunamon 14y ago
A part of the hacker mindset ("hacker" as used in the jargon file, and in this site's title) is intolerance of stupidity. Ignorance is one thing, that can be learned away. Stupidity is wasting developer's time by asking questions that are addressed in the documentation or that can be instantly solved with five minutes on Google, or submitting pull requests that go against a published style guide, are plainly wrong or buggy, and so on.
I'm going to come right out and say this: Some people should not contribute to a FOSS project. Whether that's because they can't deal with other people or because they're not willing to put in even a modicum of effort to work effectively with other people. If you go up to a group of people who are used to doing things according to procedure X and you blithely ignore it, you really should not be surprised when your efforts are met with derision at best and hostility at worst.
While I understand the point the author is trying to make here, and even sympathize to a point, the mindset isn't going to change, nor should it. The bar to entry is a part of what make high quality projects high quality.
- darkarmani 14y ago> The bar to entry is a part of what make high quality projects high quality. Maybe the code is of high quality, but they usually end up stale and defunct from lack of contribution.
- hubb 14y agoplease don't try to excuse rude behaviour by ascribing it to a culture that is defined by curiosity and tinkering. being rude has nothing to do with hacking. if you want to be curt and insult people, then you bear the onus for that.
- steele 14y agoFOSS isn't exclusively "hacker culture", and that behavior isn't correlated with high quality. If that is the accepted behavior of the maintainers/contributors, then be 'open' about that too. "If you have questions, RTF(src|wiki|docs|issues|blog|groups) then come join us in #herpderp on freenode where our chamber of @ cloaked elders will determine your fate; aid you, ignore you, berate you, or remove you."
- mion 14y agoHe's not talking about lowering the bar to entry, he's just saying you don't need to humiliate others when they are just trying to help you. You could at least dismiss them in a friendly/neutral way. "Sorry, can't accept this: check out procedure X in the docs."
- Karunamon 14y agoHence the "sympathize" part, but then again, I also sympathize with people who are human and eventually want to start inflicting bodily harm on people who can't be arsed to read the FAQ before A'ing the same Q again. Part of the "bar to entry" is that mindset. You don't get a pat on the back and warm encouragement for submitting crap code. You get told your code is crap with the expectation you'll improve before wasting the reviewer's time again. Call me crazy, but I happen to love this environment.
- mion 14y agoI know it can be a pain in the ass when people ask you the same (stupid) thing over and over again, but still, IMHO a "leader" of any kind should never bash his "followers". Or he'll end up losing them. with the expectation you'll improve before wasting the reviewer's time again When you insult people and act like a jerk I don't think you want them to come back ever again.
- eitland 14y agoYour FAQ better be very visible and better include the question and a working answer then. Also (no offense, you might be a real genius) but a lot of people who think they are above everyone else really isn't. I've seen people frown at the use of Java reflection because it wasn't type safe then go ahead and deliver brand new features written in pl/sql.
- akkartik 14y agoYou sir are a douchebag, and I won't participate in any project you're associated with. I don't understand why everyone's pussyfooting around this guy. Please? No offense? This guy is THE PROBLEM. He doesn't get a pat on the back and warm encouragement for providing crap people skills. People skills are part of a project too, just like code. I downvote rude people on HN, and ascribe to the idea of not saying something you wouldn't say in person. But this guy? I'd say this and more to him in person, on a stage, in front of a million people. Go ahead, downvote me. It's all in a good cause.
- shadowfiend 14y agoThere is literally nothing that you gain from being derisive that you can't also gain from being polite. And the tone you set for your community is vastly different. Derision of stupidity is probably one of the worst characteristics of hacker culture, because “stupidity” tends to be shorthand for “disagreement with my point of view”. I have trouble making a cogent argument around the derision of stupidity because derision should be self-evidently bad. It should automatically file under “why would I want to do this to my own personality”. Derision and bullying are indistinguishable from each other, and the thought that a group as oft-socially-maligned as hackers (at least until the last 6 years or so) defaults to derision seems more a sign of imitating things we were subjected to than reasoned thought. “If you go up to a group of people who are used to doing things according to procedure X and you blithely ignore it, you really should not be surprised when your efforts are met with derision at best and hostility at worst.” What does blithely ignore mean? Say this is the first open source project I've ever contributed to, so I don't know what the norms are in terms of where to even look for guidelines. Or I contributed 30 minutes of my time because that's all I had, and I devoted them to this. Or I'm learning to program, and I chose to try to help your project. I will posit that anyone who is trying to contribute to your project is doing you a kindness. They may be doing it in a poor way, and you are within your rights to point that out. But how you point it out is what we're talking about. You an politely point out that the project doesn't accept pull requests. You can politely point out that tickets can't be opened until there's been a discussion on the mailing list. Etc. You can even be curt. Derision is not curtness. It is not impatience. It is explicit, intentional putting-down of someone because they aren't as good at something as you are or think they should be. And it is a poison. Unfortunately, if you take it frequently enough, it becomes habit. It becomes second nature. And you stop noticing it's poisonous. And so, unfortunately, it is an oft-enjoyed poison in intellectual circles. It doesn't help anything. It doesn't help you understand the world or other people. It doesn't really save you that much time. It simply makes you feel better about yourself.
- Karunamon 14y ago>Derision of stupidity is probably one of the worst characteristics of hacker culture, because “stupidity” tends to be shorthand for “disagreement with my point of view”. Then it's not stupidity. That's not what this article (at least that I can see), or my post, was talking about. I was referring specifically to failure to RTFM as the big one, with a side order of bad commits and pull requests. Ask any tech support monkey at the end of their day what they think about the average person. Then remember that this person is getting paid to do it. How do you think someone who rolls a project as a labor of love feels? And anyways, if you have an open source project, and it's set up in such a way that commits have to be approved by one person or a group of people, then that one person or group of people are the only people who's point of view matters, at least when it comes to that code in that project. Don't like it? That's what forking is for. >Derision and bullying are indistinguishable from each other Disagree. Derision is a society's way of pointing out that you did something you shouldn't have. I have absolutely no problem with mocking stupidity. Stupidity is evil and everything wrong with the world, and should be mocked and driven out mercilessly at every opportunity. And you'll forgive me for thinking that pointing at a silly pull request and saying "wat" isn't even on the same ballpark as "bullying". >What does blithely ignore mean? Okay, as an example: https://developer.mozilla.org/en-US/docs/Introduction https://developer.mozilla.org/en-US/docs/Introduction A well defined process and a very good guide to what you should do if you want to help. Ignore means just that, "ignore". If you got a pull request into that system, then you obviously got ahold of that information some way. >I will posit that anyone who is trying to contribute to your project is doing you a kindness. But if you're wasting people's time, then that effort is wasted, and having the opposite effect at worst. That time spent dealing with your question which is answered in the docs or telling you why your pull request isn't going to be committed could have been better spent advancing the project. Time is valuable.
- jasonlotito 14y agoStupidity is defined by wasting time responding to questions with insults and derision.
- mindcrime 14y agoA part of the hacker mindset ("hacker" as used in the jargon file, and in this site's title) is intolerance of stupidity. I totally disagree with this. Yes, a lot of hackers may have an "intolerance of stupidity" but I don't know of anyone who has the right to define "hacker" who can say that the definition includes that. And never mind the fact that we are ALL "stupid" in some domain or other and we all do stupid things every day.