News for hackers. Stuff that matters.
Re:The Cancers In The Ruby Community by GussyGusGus on Sunday April 15, 2012 @04:06PM (#3844563)
All three of those things are merely symptoms of the real problem: a lack of professionalism.
Re:The Cancers In The Ruby Community by philwelch on Sunday April 15, 2012 @04:55PM (#3844717)
I don't think it's so much a matter of professionalism as much as lazy thinking. For instance, the notion of "best practices" is utterly professional, but when overapplied or misapplied it results in some of the same symptoms.
Re:The Cancers In The Ruby Community by petercooper on Sunday April 15, 2012 @06:07PM (#3844932)
Re:The Cancers In The Ruby Community by nupark2 on Sunday April 15, 2012 @08:19PM (#3845278)
"Professional to me is facade, fake sincerity, political correctness, not offending anyone, and everything else that makes life lifeless."

Which only goes to support the notion that much of Ruby's community has issues from the top down. We're speaking of computer science, in which objective, rational analysis leads to correct answers -- not appeals to emotion and an almost religious acceptance of poor solutions.

For every serious Ruby contributor and leader like Charles Nutter (JRuby), there are 5 DHHs or DDH adherents shouting down professionalism as if it was an anathema to logical expression.

Re:The Cancers In The Ruby Community by petercooper on Monday April 16, 2012 @04:27PM (#3849241)
I agree, I think DHH's statements were bizarre. They seemed to assume a sort of binary idea of "professional." You were either an anal retentive, by the book pedantic clock puncher or you were a fun loving rock star. The truth is there's a wide gamut and I think it's great for people to be "professional" without going to some sort of IBM-style extreme.
Re:The Cancers In The Ruby Community by ccashell on Tuesday April 17, 2012 @09:41PM (#3856037)
Times change. IBM-style "professional" is not the "anal retentive, by the book pedantic clock puncher" you might think. I worked there over 10 years ago, and we had no written dress code, flex-time scheduling, remote work, etc. The building I worked in had a 9 hole putt-putt course outside it, with foosball tables in a couple of the stairway landings.

Interesting how long we can hold on to perceptions from the past, even when they've been wrong for over a decade.

(I'm not implying that I'm disagreeing with you, in fact I think this shows that even what people think of as "pedantic clock puncher" and "fun loving rock star" from the outside is often very different on the inside.

Re:The Cancers In The Ruby Community by tomjen3 on Sunday April 15, 2012 @05:50PM (#3844883)
Please.

Professionalism is what is killing great languages like C# and decent languages like Java.

It is just an excuse for those in suits to look down on the rest of who create software because we fucking like it, in a way we like, rather than in a way that doesn't threaten them.

Re:The Cancers In The Ruby Community by protomyth on Sunday April 15, 2012 @06:05PM (#3844928)
Professionalism has very little to do with the "suits". In fact, I have seen that programmers are made to do our least professional work when some out-of-touch manager makes their decisions.
Re:The Cancers In The Ruby Community by chromatic on Monday April 16, 2012 @01:42PM (#3848433)
Professionalism is what is killing great languages like C# and decent languages like Java.

How so?

Re:The Cancers In The Ruby Community by rollypolly on Sunday April 15, 2012 @04:21PM (#3844609)
How do you fix lack of professionalism?
Re:The Cancers In The Ruby Community by derefr on Sunday April 15, 2012 @04:28PM (#3844632)
You don't. Non-professionals will become professionals with time and experience, but there will always be more non-professionals to take their place. The only reason some communities have to deal with more non-professionals than others, is that those communities are perceived to have a lower barrier to entry--so, when a non-professional tries to select a community to join/language to learn/tool to use/etc., they end up with the "easier" one, and thus the "easier" community builds a reputation of non-professionalism. The only real measure one can take to avoid this is to make the community unattractive to non-professionals: in est, to raise the barrier to entry.
Re:The Cancers In The Ruby Community by FooBarWidget on Sunday April 15, 2012 @06:17PM (#3844961)
I don't think barrier to entry is the only factor, if it's a factor at all. The Linux desktop has a relatively high barrier of entry, and yet a large part of its community has devolved into an elitist, cognitive dissonant crowd that's defending their usability problems by framing them as a good things.
Re:The Cancers In The Ruby Community by hjhjhj on Sunday April 15, 2012 @04:44PM (#3844688)
lol he said "professionalism". Feels like 1997.
Re:The Cancers In The Ruby Community by clivestaples on Sunday April 15, 2012 @05:11PM (#3844770)
Common courtesy, decorum and a prevailing sense of personal responsibility are lost in these frothy times of high demand and inflated economy (i.e. the fast train to DoucheVille). But one day this economy is going to correct in earnest and all these allusions of grandeur are going to give way to some harsh realities. Being too-cool-to-act-professional is going to make a lot of mustaches sad.

Effective smart people are humble and kind (like Matz). Blowhards are insufferable douchebags and no amount of fake rebellion against 'professionalism' is ever going the change that.

Re:The Cancers In The Ruby Community by hjhjhj on Sunday April 15, 2012 @09:18PM (#3845453)
Sorry, maybe I should elaborate. Professionalism is the act of work for pay. Exactly what you just denounced.

I've worked for many places where we joked about being "professionals" simply due to the fact that we were being paid.

The term "professionalism" is a dinosaur that has nothing at all to do with quality or attitude or really anything beyond someone paying you.