Hacker News Reader

Comment by lifeisstillgood | Hacker News Reader

I am not terribly sure that these single issue job boards are the best idea ever, or pointless dead ends. The Python job board is a great example - it's been around for years and I always advertised positions I had on it, but for the life of me I cannot think of anyone I know who ever got a job through it.

I think when you are looking, you go to the big sites first and then there is soooo much there then looking in the sensible one issue places seems silly

Then again, one could do a lot worse than provide a job board for every <Lang>.org site out there.

Edit: PS you have hit a quota limit so I can't comment beyond the generic rant above :-)

View on HN

I don't really really agree with the idea of [New Framework X] job boards either. Languages, I get: if you know Language Y, you can probably pick up Framework X in a few days, and by the second week no one will know you came in without knowing it. Honestly, extend the timeline by another week or so and you can apply the same to languages (with talented devs at least).

Personally, I don't consider myself an Angular developer - I'm a developer (a "full-stack developer" if I had to qualify the term somehow). I can pick up any Javascript framework in a reasonably short amount of time, because I have a lot of experience with the language.

Furthermore, who's to say you'll still be using Framework X a year from now? Your needs will change, and all of a sudden the premium you paid for that specialized talent is money wasted. Just hire talented developers - they'll learn whatever stack you throw at them, every time.

Appreciate the comments guys, you may very well be right! However, I suppose it could come down to something like this, for example - one may have a project which has Angular embedded deep within it. You want to hire an Angular dev - someone who knows it inside out, not just a "front end JS dev" who can possibly pick it up - needs may change, but for said project you need an Angular dev. Or perhaps the type of person that loves Angular and the way they think is who you are trying to hire.

I think as well that something like Angular which seems to be going mental at the moment is an indication of a change of thinking for doing front end work, so even though frameworks come and go, maybe the desire to hire an Angular dev is more about hiring someone who is embracing this change of thinking.

I'm sure there are lots of reasons for and against but time will tell if a) employers actually get candidates from this board and b) do developers find interesting jobs from this board.

I would prefer "hire curious but professional developers" - and let them choose the stack most appropriate to your needs. They will not run off and build with the latest and greatest, but will focus on their TCO. So yeah hire good people pay them well, give them space, trust them to run your business for you. Don't hire contractors except me.

I personally think Js heavy clients are going to stay, and more importantly, one will win out as the 'Win32' standard, to the extent that many sites will not send me any custom executable code because that is easiest to avoid attacks.

And it think angular is ahead in the (still to finish) race.

I completely agree with this. The best thing I ever did was tear apart the popular JS frameworks of the day two-three years ago and now I can pick up any of these JS frameworks in a day or two for the most part.

Hire programmers, not members of the Church of #{latest_framework}.

They are a bit like "social network for dog owners" approach. There's this huge chicken and egg problem of bringing the advertisers and job hunters together to a job site and the first thing that comes to mind is to take a stab at a vertical. It rarely works.

+1. Keep in mind in 2011 you would have had 'We Love backbone.js' - which wouldn't be so popular nowadays.

Yeap, tying one's job title / website to a JS-framework of the moment - what a terrific idea.

Reply on news.ycombinator.com