News for hackers. Stuff that matters.
Re:Modern Ruby Development by rhizome on Tuesday September 27, 2011 @07:41PM (#3045769)
Too much cool new stuff, why not just work out the bugs in the existing projects instead?

This may not be a popular opinion, but I have a suspicion that the high degree of wheel reinvention in the world of Ruby and Rails libraries is due to two things: NIH Syndrome & the professed preference by employers for people with active GitHub projects. This causes all kinds of people to make their own gems and such where existing implementations could be improved without such a division (diffusion?) of labor.

Re:Modern Ruby Development by damncabbage on Tuesday September 27, 2011 @08:09PM (#3045858)
I'm definitely feeling the push to show that I'm doing something on my 'Hub account. I can see why it'd be tempting to go and reinvent a wheel to give that impression.

To make it worse, GitHub only occasionally shows commit activity on repos belonging to other people. I have plenty of side-projects going over on a communal account at http://github.com/smashcon. If I work on some of those repos for a couple of weeks, however, to the casual observer it appears as if I haven't been doing anything at all.

(The canonical answer appears to be "fork and use pull requests", but at this point in the project they're just too clumsy for little benefit, particularly each only has a single committer.)

Re:Modern Ruby Development by benatkin on Wednesday September 28, 2011 @05:11AM (#3047093)
On the other hand, if you get someone else to commit on a project you start, people will think of you when they think of the project. Case in point: until I looked at the history in-depth I always thought of pengwynn when I looked at this project:

https://github.com/pengwynn/faraday_middleware

The vast majority of commits are by https://github.com/sferik though.

I don't think pengwynn is gaming the system, but if someone wanted to, this is how they could do it.

Re:Modern Ruby Development by bphogan on Tuesday September 27, 2011 @11:24PM (#3046316)
I love that things change, and I love the almost competitive nature between projects, but it's grating if you maintiain existing things.

If you're a consultant hopping from one client gig to the next each few months, it's great. If you maintain your own things, it gets frustrating when things you relied on are no longer maintained because the developer got tired of putting up with putdowns about how his project "sucks" and [x] is the new hot way to log people in. :)