News for hackers. Stuff that matters.
Re:How to hire the best people you've ever worked with (2007) by rumcajz on Wednesday December 23, 2015 @09:04PM (#10786701)
> REST vs SOAP, the new Facebook API, whether Ruby on Rails is scalable, what do you think of Sun's new Java-based scripting language, Google's widgets API, Amazon S3, etc.

Really? Why would anyone learn any of that unless they actually need it to make their work done?

Re:How to hire the best people you've ever worked with (2007) by overgard on Wednesday December 23, 2015 @09:16PM (#10786732)
Because learning that kind of thing increases the possibility space of what you can do. Insights usually come from a diversity of knowledge, if you only learn what you need to know you'll be exceptionally average.
Re:How to hire the best people you've ever worked with (2007) by DavidWoof on Wednesday December 23, 2015 @11:00PM (#10787052)
I agree in theory, but the problem is that everybody has their own personal "10 most interesting things right this moment" list, and they often don't match up even (or especially) among excellent programmers.

So the fact that somebody isn't spending time with your favorite new toy doesn't mean they're not constantly learning, especially when the top 10 list is as ridiculously subjective as the one in the article.

Re:How to hire the best people you've ever worked with (2007) by AnimalMuppet on Thursday December 24, 2015 @01:19PM (#10789069)
That's not his point. He doesn't care that your list is different than his; he cares that you have one.
Re:How to hire the best people you've ever worked with (2007) by KaneMorgan on Thursday December 24, 2015 @12:38PM (#10788906)
I read it as they should be interested in something, not they should be interested in what you're interested in.
Re:How to hire the best people you've ever worked with (2007) by autotune on Wednesday December 23, 2015 @11:09PM (#10787073)
Messing around with an API in your off time is important because it means you can change contexts and get up to speed more quickly without having to learn everything from scratch on the job, and of course context is everything. I'm probably not going to be super into a social network's API but for things that are server-related? Damn right I want to know how build 30 servers with just a POST request, a for loop, and some json data. You can then apply that knowledge to something a bit more boring you might get hired for if needed, like a startup that needs someone who can answer questions about how to properly use their API to make a number of POST requests to send hundreds of orders of glitter to various companies who have not sent a response to said persons job application... in theory of course.
Re:How to hire the best people you've ever worked with (2007) by ohyes on Wednesday December 23, 2015 @11:50PM (#10787160)
No it doesn't. It means you have a lot of free time and can be used as cannon fodder for the startup. You will work 80-100 hour weeks producing exceptional work for compensation that is below the area average.

Let's get real, employers /want/ young naive fresh out of college kids who've never been burned and don't know any better than to give their early to mid twenties to a VC/startup for peanuts. Messing around with a rest API is just a sign that you are potential prey, a fresh kill for the hamburger machine.

Re:How to hire the best people you've ever worked with (2007) by AYBABTME on Thursday December 24, 2015 @10:47AM (#10788485)
Or it means that among the hobbies you have that consume your free time, there is 'tech' as a line item. There's nothing wrong about doing research in tech in one's free time if that what they enjoy doing.

It's really annoying to read replies like yours that systematically suggest all people who spend time researching and side-projecting stuff about tech are doing so because they have lot of free time or are cannon fodder. If you prefer to spend your free time gardening or brewing beer, that's fine. It's equally fine if I enjoy spending my own time learning about more tech stuff.

Re:How to hire the best people you've ever worked with (2007) by ohyes on Thursday December 24, 2015 @12:02PM (#10788754)
I didn't mean to suggest that people who research and side-project tech stuff are universally cannon fodder or have otherwise negative loser-y properties. I certainly don't believe that as I do it myself...

What I meant to suggest is that there is a certain cynical undertone in an organization where 'work is also my hobby' is a disproportionately desirable line item in an interview. I was attempting to project that attitude rhetorically. Given your offense, I think the point was made, but maybe too subtly... It is an offensive attitude. To me it implies something negative about how I (and my time) will be valued.

This isn't to say anything about the (what I think is) natural 'starting a new job' period, where one puts in extra hours to get up to speed on the technologies being used and the existing code-base. That's part of hitting the ground running and being a good and productive hire.

Re:How to hire the best people you've ever worked with (2007) by marshray on Friday December 25, 2015 @02:41AM (#10790675)
These are not necessarily contradictory positions.

Even if you work only 40 hours a week directly developing software for the startup, the independent time you spend self-educating and researching can often enable faster development.

Re:How to hire the best people you've ever worked with (2007) by autotune on Thursday December 24, 2015 @12:11AM (#10787201)
> You will work 80-100 hour weeks producing exceptional work for compensation that is below the area average.

This is what glassdoor reviews are for, and is entirely dependent on the company. Besides that it's a two way street, you bolster up the resume and if it turns out it's not what you expected than you now have the skills to find an environment that is what you're looking for. Alternatively you could of course spend your early-mid 20s being homeless and join the gutter punks in trying to sell weed to those VCs around The Haight instead, but that's not as fulfilling or lucrative IMHO.

Re:How to hire the best people you've ever worked with (2007) by tamana on Wednesday December 23, 2015 @11:55PM (#10787172)
You said it yourself, these candidates produce exceptional work. The fact that they may be underpaid is a problem with their (group) ability to negotiate pay, not a failure in hiring manager's talent recognition.
Re:How to hire the best people you've ever worked with (2007) by mattmanser on Thursday December 24, 2015 @04:34AM (#10787654)
To be fair this was 2007, they were interesting things at the time that you might plausibly muck around with for a side project.
Re:How to hire the best people you've ever worked with (2007) by wyclif on Friday December 25, 2015 @04:54AM (#10790829)
Keep in mind this was written in 2007. I don't think all of that stuff is irrelevant by any means, though. Nine years later, the list might look somewhat different, but his point is that it's an indicator of intellectual curiosity, not things that are directly practical for the job the employer is offering.
Re:How to hire the best people you've ever worked with (2007) by AYBABTME on Thursday December 24, 2015 @10:39AM (#10788468)
Because they're curious about it? The same as they might be curious about the geology of Mars and the history of the world since the Renaissance. Maybe just for the kick of it, or because they have a side project in mind.