News for hackers. Stuff that matters.
Re:Coderwall (YC W12) Wants to be the Reputation System for ... by tomjen3 on Monday February 27, 2012 @03:07PM (#3640406)
What problem is it that you are trying to solve, exactly? That it is hard to find good developers? It is, but that is not because they can't be found (in which case your app might help) but because there isn't enough of them to go around at the current price point, which means that nearly all the good ones have a job and if not, they will be able to get one reasonably fast. Simply getting more companies to bid on the good ones won't do much, as most companies won't let you work more than one job and most developers wouldn't want to anyway.

If you really want to end the shortage then you either have to drastically increase salary, pricing most companies out of the range and thereby cutting demand, or you have to create a lot more developers.

If you want to make it easier for the companies to hire, then you could become company change consultants and work to change the companies into places with no bullshit and where developers are actually respected. That would be awesome from our perspective, and from the perspective of the economy but is properly also the least likely.

Re:Coderwall (YC W12) Wants to be the Reputation System for ... by paul on Monday February 27, 2012 @04:21PM (#3640708)
That's not entirely true. A lot of very talented people are being wasted at bad jobs. In many cases, they don't even realize it because one of the features of a bad job is that it will often make you feel bad about yourself (as with other types of bad relationships). There would be a lot more "good developers" if everyone were in the job that is right for them.
Re:Coderwall (YC W12) Wants to be the Reputation System for ... by jfarmer on Monday February 27, 2012 @04:50PM (#3640816)
I agree that a good portion of the "hiring crunch" right now is an issue of mis-allocation rather than raw under-supply.

Yahoo! has tons of great engineers working on really hard technical problems. What qualified engineer there wouldn't be better off at even, say, Facebook? The engineers who work on Sherpa, for example, are highly qualified.

I have a hard time seeing Coderwall as the solution, though. (Not that you're arguing that it is.)

Why?

The core design decisions in the product are going to attract the kind of people who like to show off. Badges? Achievements? Public profiles styled a la the Facebook timeline?

Those are the engineers who, by and large, are already showing off. They have public personas, whether on GitHub, Twitter, major projects they contribute to, or just being "personalities" in their community.

The product that gives exposure to engineers hiding inside companies like Yahoo! needs to be something less, well, game-like. I'm not sure what that looks like, but that's my first impression of Coderwall.

It feels like a cargo cult. All these little gamey doodads don't add up to a coherent thesis about how to get engineers more exposure. It feels more something that came out of this kind of conversation:

  Person A: Hey, we need to increase engagement.  How can we do that?
  Person B: Achievements!  That'll do it!
This is why GitHub is so marvelous. It didn't start out with the idea of getting engineers more exposure. The exposure is a side effect of making it easier to contribute in public than in private. That'd be my starting point for doing something really radical: what can we make public that used to be private, in a way that excites developers?

Making GitHub activity "even more" public, or aggregating it in a way that's easier for non-technical people to consume, is probably not the first thing I'd try. It is the easiest, though. (For me, that's a reason not to do it, rather than a reason to do it.)