News for hackers. Stuff that matters.
Re:Skills Don’t Pay the Bills by zmmmmm on Sunday November 25, 2012 @01:07AM (#4827455)
I see a similar problem even in software jobs. Employers frequently advertise for highly specific skill sets that almost nobody has. Then when nobody or only fraudulent people apply, they reject them all and claim a skills shortage. The problem seems to be a basic misconception about how transferable software skills are. An excellent programmer with no experience in Python will be out performing a poor Python programmer in a matter of weeks, even though they have had to learn an entirely new language. This idea, however, seems entirely lost on most HR departments, and the result is an almost entirely "fake" skills shortage.
Re:Skills Don’t Pay the Bills by mseebach on Sunday November 25, 2012 @02:25AM (#4827567)
It's not just HR. I did an interview with a YC startup that obsessed over my lack of Rails experience. I have several years of industry relevant professional experience in Java, Python and PHP, but only ever dabbled in Ruby and Rails. Their offer (which did come through, grudgingly, through many repetitions of "so will you commit to teaching yourself rails before starting?" (No, I won't.) was quite a bit on the low end, but I'd probably have turned it down anyway for that strange lack of comprehension of programming skills.
Re:Skills Don’t Pay the Bills by codewright on Sunday November 25, 2012 @04:29AM (#4827760)
I've had a lot of encounters with YC founders, most of them negative.

This anecdote well encapsulates the impression I had of a lot of them.

I'd really like to meet the better of the crop, because I can't imagine PG and Jessica (she's usually the expert on character and personality in YC interviews) are intentionally picking petty people.

I'm not the only person in the startup industry who's had this impression either. They remind me a lot of underqualified legacy Harvard kids who think they're god's gift because they snagged a status symbol.

Maybe the better founders are too busy shipping product to run into me :)

Re:Skills Don’t Pay the Bills by brudgers on Sunday November 25, 2012 @08:45AM (#4828126)
Leaders may be born, but management skills are learned from experience. Those skills require conscious thought to implement because they are antithetical to the natural inclination to abuse power disparities within a relationship.

Using management skills as a primary selection criterion would be premature optimization in YC's process. At some point, hopefully HR is screening rather than the founders, but early on putting up with the founders' bullshit is part of a necessary skill set.

Re:Skills Don’t Pay the Bills by moultano on Sunday November 25, 2012 @04:53AM (#4827789)
I can imagine that for a company with a runway measured in months, immediate skills might be more important than for a well established company.
Re:Skills Don’t Pay the Bills by yummyfajitas on Sunday November 25, 2012 @10:03AM (#4828269)
I'm not sure about this.

When I was at my startup, I hired a guy with no Django experience and minimal python. He made his first bug fix within 24 hours of showing up and was productive within a week.

Maybe RoR has a much steeper learning curve, or maybe the people doing the hiring just don't get it.

Re:Skills Don’t Pay the Bills by codewright on Sunday November 25, 2012 @08:11PM (#4829914)
>When I was at my startup, I hired a guy with no Django experience and minimal python. He made his first bug fix within 24 hours of showing up and was productive within a week.

I had the same experience with Django walking in with the same repertoire (minimal Python, no Django) back when I lived in NYC.

I don't do Django anymore, but it taught me a lot about trusting people to pick things up on the fly. Especially with the right person and environment.

Re:Skills Don’t Pay the Bills by codewright on Sunday November 25, 2012 @06:07AM (#4827884)
Specific skills weren't the issue in my interviews. I was remarking more on the pettiness of the founders I talked to.

That aside, both of my interviews at YC companies (two, although I've talked to a lot of YC'ers besides), had profitability so the typical runway concerns weren't predominating their conccerns I would think.

Re:Skills Don’t Pay the Bills by waterlesscloud on Sunday November 25, 2012 @04:15PM (#4829307)
In that case what's the cost of having the position completely unfilled for a month or two?

Seems like it would be so drastically high that hiring a MVC (Minimal Viable Candidate) might be the right choice.

Re:Skills Don’t Pay the Bills by npsimons on Sunday November 25, 2012 @05:24PM (#4829502)
This was my first thought, although it comes from my POV where I think I am a slow learner because I can't pickup a new programming language over a weekend. I'm still exploring the dark corners of C++ after a year or two, but mostly that's due to the demands of the current and previous project. I went through the whole Python tutorial once, to never use it much again, then flubbed a Google on-site because of it. On the flipside, when given a week to work up some post-proc analysis code and the opportunity to do it Python, I was up and running in a little less than a day. It's amazing what you can do when you have access to reference materials and more than 60 minutes.
Re:Skills Don’t Pay the Bills by jokull on Sunday November 25, 2012 @11:54AM (#4828522)
But how were they supposed to know you were the kind of programmer that picks up a new language in a matter of days or weeks? Most programmers take years to become competent in a language. I think this hiring practice, although unfortunate, is just the employer securing themselves in case the programmer is only at medium competency. Then at least he or she can use that one language where they have shown at least some competency.
Re:Skills Don’t Pay the Bills by losvedir on Sunday November 25, 2012 @10:51PM (#4830386)
You're deluding yourself if you think you'd be as valuable to an early RoR-based company as a good dev with a year of Rails experience. I used RoR for my start-up because I was sick of PHP and wanted to learn Rails, and I feel immensely more productive now than I did when I began. And I'm a "quick learner", too.

Familiarity with Active Record, and making it reasonably performant, handling rails security issues, experience with the gem ecosystem, understanding the intricacies of the routing DSL, getting a handle on reasonable rspec/capybara or cucumber practices, ruby metaprogramming, knowing the Rails conventions and what it looks for automatically in controllers, views, and partials, and which methods are available where, knowing all the various helper methods rails provides for text processing, working with dates, and html tags, best practices integrating with AJAX, migrations, rack middleware, the asset pipeline, etc, etc. I've been working on our Rails app non-stop for 9 months now and every day I learn new stuff.

Long story short, for a start up which needs to iterate fast before it dies, acclimating a competent programmer to the "Rails Way of Life" just might not be worth it. Now, it's a completely different story if you have important domain specific knowledge, and the company is working on something especially innovative, but it seems like a lot of start-ups are scrambling for a pretty low-tech piece of the pie where "execution wins". My point is, Rails is surprisingly big, and while you can become useful in a matter of weeks, you can't become extremely productive with it for awhile longer.

Re:Skills Don’t Pay the Bills by redguava on Sunday November 25, 2012 @03:21AM (#4827657)
I don't see a problem with requiring Rails experience. It depends on the job of course. If I don't mind a slow ramp up and want someone right for the job that might last a few years then I don't care. If I have some complicated technical issues I need fixed quickly, I want someone that can jump in and go right away.

Particularly with Rails where it's convention over configuration, knowing the conventions is a great headstart.

Re:Skills Don’t Pay the Bills by venomsnake on Sunday November 25, 2012 @04:16AM (#4827742)
Then you probably need consultant if it is only for a specific issue. Otherwise once this is solved you got bored to death employee, with skill set for which you are overpaying and under-utilizing.

Unless you need language guru, the languages known don't matter much. If someone can write a LISP interpreter in Haskell for 2 days I would hire her for a Java position even if she doesn't know what a loop is.

Re:Skills Don’t Pay the Bills by capisce on Sunday November 25, 2012 @08:10AM (#4828060)
Except that person is going to bounce as soon as a better opportunity (not involving Java) comes along.
Re:Skills Don’t Pay the Bills by raverbashing on Sunday November 25, 2012 @04:09AM (#4827735)
There are two sides to this:

Either you have another skill that they need, or they just want a "generic (good) rails programmer"

Of course skills are transferrable, within a timeframe. So if you're trying to ship something in 6 months this may not be acceptable

Re:Skills Don’t Pay the Bills by maigret on Sunday November 25, 2012 @09:18AM (#4828188)
Usually there are two skills to have to ship a software project:

- Knowing and using the basic underlying technologies (languages, but also concepts, like machine learning, databases, UI skills or so on)

- Knowing the specific codebase and process for those projects (how the build works, what are the components, what they do, etc).

True, someone knowing the first skillset has an advantage, but a talented person will have no problem doing the second one much faster. For an hire, I would rather factor in the long term. It's about sane finance management and ROI, actually. For any given pool of candidates, you are considerably reducing the chance you hit a talented people, if you interview only 10% of all candidates just based on their previous base skills.

Re:Skills Don’t Pay the Bills by eli_gottlieb on Sunday November 25, 2012 @01:19PM (#4828771)
I got competent with Rails in 1 month. It would have taken less time if my boss hadn't had to run away for a week and a half and leave me with tutorial/study work rather than real meat I could cut my teeth on.

EDIT: Actually, I want to tell more of this story to emphasize what you can do with a reasonably competent employee willing to learn.

At the time, I was hired as a temporary contractor for 3-4 months. I had basically most of 1 month to get to basic competence with Rails, and it was supposed to be less. Then I started getting real work thrown at me. By the end of 3 months, I had justified my pay and my employers had no more temporary work to throw at me. They offered to hire as a full-time salaried employee, but by then I had a plan for grad-school and research.

That was at the end of June. Midway through November, my friend who originally recommended me to that employer messages me on Facebook. He tells a bit of an ironic story, one point of which is that he himself is now using and expanding-on the code I wrote in those two-point-something months. Apparently it's holding up pretty decently, and the team is able to ship product.

All this because the proprietor of the firm figured he could hire someone smart with a good work-ethic for a while and give him time to get competent with Rails rather than go unicorn hunting.

Re:Skills Don’t Pay the Bills by enko on Sunday November 25, 2012 @02:46AM (#4827608)
I think a core problem is "HR" departments with absolutely no understanding of the positions they are supposed to be hiring for, even for technology companies where technology is supposed to be a core competency.

The only thing stopping me from calling out HR departments in general as a sign of organisational cancer, since I am yet to encounter one that pulls even a tenth of its weight, is that they tend to be comprised of the only cute girls in the whole company. Even on Friday (2 days ago) I was out drinking with a bunch of tech guys and a single cute HR girl. That is pretty much the sole reason I would oppose eliminating HR as we know it from all technology companies.

Re:Skills Don’t Pay the Bills by kabdib on Sunday November 25, 2012 @04:43PM (#4829387)
++ on "HR doesn't understand the tech"

I had a phone interview once where the person on the other side was (the hiring side) was trying to suss out my skills.

"Do you know real-time object-oriented programming?" they asked.

"Well, I know object-oriented programming, and I've done a lot of real time stuff, so: Sure."

"No, I think you're trying to fool me. Please answer truthfully, do you know _real-time object-oriented programming_?"

"Yes."

"I don't believe you."

Things went downhill from there. The interviewer clearly had no idea what they were actually asking, and it was impossible to express any competence other than to repeat buzzwords.

Bottom-line is: That company missed out on a great employee. They utterly blew it.

[Yeah, I know you only have my word for this. Suffice to say that I have enough objective evidence from subsequent projects and employment that I know I'm not Dunning-Krugering myself.]

Re:Skills Don’t Pay the Bills by jimbokun on Sunday November 25, 2012 @08:10PM (#4829910)
I had a phone interview once where the person on the other side was (the hiring side) was trying to suss out my skills. "Do you know real-time object-oriented programming?" they asked.

I would be so tempted to reply "Do you?"

Re:Skills Don’t Pay the Bills by eshvk on Sunday November 25, 2012 @03:37AM (#4827696)
Nice, very classy of you. Tell me again, how does it feel to time travel here from the fifties?
Re:Skills Don’t Pay the Bills by enko on Sunday November 25, 2012 @03:54AM (#4827711)
Why, did they tell the truth in the fifties or something? I assume "classy" is your stand-in word for politically correct.

I can see that no-one likes what I said but I assure you it's my honest feeling. HR departments' best contribution to an organisation is cute HR girls. You can deny this truth, or perhaps try to change the way of things. Clicking to downvote me, of course, changes absolutely nothing.

Re:Skills Don’t Pay the Bills by pinaceae on Sunday November 25, 2012 @04:30AM (#4827763)
well, it is a correct observation that HR (and marketing) departments have the highest female ratio in pretty much any company.

let's look at famous examples: Carly Fiorina? Marketing. Brigitte Ederer (Siemens)? HR. Meg Whitman? Marketing (started as a Brand Manager)

the cute moniker is unnecessary, I agree. the overall observation is correct.

i agree in particular with the fact that once HR takes over hiring from the team-leaders, the company has jumped the shark. one of the core tasks for a manager is hiring, ensuring his/her team is correctly staffed and has enough fresh blood to ensure senior people can move upward or away without disruption. if you don't, the Peter principle is in play.

overzelous HR is the ruin of a company because by definition HR has no clue about the core competencies of a company, no feeling for its customers nor products/services.

Re:Skills Don’t Pay the Bills by eshvk on Sunday November 25, 2012 @04:41AM (#4827773)
You are missing the point and flailing at straw men. I don't care about the female ratio (Neither I think does any one who downvoted the OP). I am not going to discuss the utility of the HR department, the issue here is that they are human beings whom no one has the right to reduce as being mere eye-candy (which is particularly freaking sexist).
Re:Skills Don’t Pay the Bills by enko on Sunday November 25, 2012 @04:58AM (#4827794)
> I am not going to discuss the utility of the HR department, the issue here is that they are human beings whom no one has the right to reduce as being mere eye-candy

this attitude, to me, is unbelievable. Of course they are human beings. What else would they be?

If you're going to make a claim about HR, make it on its merits. I have said they're nothing but a bunch of good looking girls. They have zero understanding about any of the roles they're hiring for, and no incentive to learn. Care to contradict me?

Re:Skills Don’t Pay the Bills by wazoox on Sunday November 25, 2012 @09:32AM (#4828221)
I've been interviewed at a few large tech companies in the past 15 years, and the HR guys were... well, guys. And not remarkably good looking. I'm afraid that your opinion is just that, your opinion. And it's a sexist one with that.
Re:Skills Don’t Pay the Bills by enko on Sunday November 25, 2012 @02:53PM (#4829062)
> your opinion is just that, your opinion

And I never claimed otherwise. But I really resent your accusation of sexism, since I believe I am extremely fair to both sexes.

It is a plain fact that the attitude towards HR departments here is mostly negative. It is another plain fact that those departments are mostly female. If these facts are sexist, then reality is sexist.

Oh, and the all-male "IT department" is also richly deserving of criticism, though not by me since I jumped that ship long ago. I look forward to your devout claims of sexism when such a criticism does occur, however.

It boils down to this: if you put the wrong people in charge of very important stuff, then (long term) you are fucked.

Re:Skills Don’t Pay the Bills by lincolnq on Sunday November 25, 2012 @03:25PM (#4829171)
OK, I'll bite. Your social error, leading to claims of sexism, was linking bad HR people and women.

I believe you when you say that's what you've observed. But, whether you like it or not, it's not okay (in public, at least) to make statements which link gender, race, etc., with competence.

No fair, you (or some other reader) might say. I'm just reporting my observations. But I claim that you have a responsibility to do more than simply report your observations, and it's because people are stupid. When we read "A and B go together," we humans immediately and instinctively (system 1) draw causal conclusions about A and B. It doesn't matter if it's anecdotal evidence; it doesn't matter that correlation does not equal causation. Not for System 1, anyway. And those causal conclusions lead to making bad subconscious assumptions, and later lead to actual sexism down the road. All because of comments like yours -- "A and B go together".

So don't do it. Suppress your urge to report your observations when they could lead to others making sexist/racist assumptions in the future. Bad HR department? Say "bad HR department" and leave the part about gender out.

(I would say that this only applies to speaking/writing in public. In private, you know who your audience is, and what conclusions they will draw from your words, so you can afford to be freer.)

Re:Skills Don’t Pay the Bills by Dylan16807 on Sunday November 25, 2012 @05:51PM (#4829560)
>linking bad HR people and women

You seem to be fundamentally misunderstanding the original complaint. The idea was that HR itself is a problem. It's not about people being bad at HR. And your suggestion to 'Suppress your urge to report your observations when they could lead to others making sexist/racist assumptions in the future.' deeply bothers me. If we pretend things don't exist because they look sexist/racist/etc, we get in even deeper problems of trying to figure out what is real.

Re:Skills Don’t Pay the Bills by nostrademons on Monday November 26, 2012 @12:07AM (#4830641)
People are responsible for their own stupidity.

(Although personally, I don't see what the gender of the HR department adds to the discussion anyway.)

Re:Skills Don’t Pay the Bills by enko on Monday November 26, 2012 @11:57AM (#4832750)
> People are responsible for their own stupidity

No doubt, but this doesn't scale. Right now you and I both are suffering from bad hiring decisions from local government up. I cannot wait for the great wheel to turn and bad hirers to be punished in the afterlife.

> I don't see what the gender of the HR department adds to the discussion

HR is a girl's club, just like IT is a boy's club, and deserves to be called out as such. The gender is relevant, indeed central.

Re:Skills Don’t Pay the Bills by TheAmazingIdiot on Sunday November 25, 2012 @11:31AM (#4828471)
"Wah Wah Wah horrendous sexual remarks Wah Wah Wah closet feminist Wah"

I think this about sums up the comment. You mentioned cute women in HR as ones who are cute and don't know about the job to properly hire.

The next avenue to attack is "denigrating" booth 'people' because we are not allowed to hilight the obvious sexuality of the (shudder) women.

Re:Skills Don’t Pay the Bills by Dylan16807 on Sunday November 25, 2012 @05:54PM (#4829572)
Where did he contrast cute women in HR with anyone else in HR? Oh wait, he didn't. You're objecting to a sexist comparison that never existed. The guy just dislikes HR.
Re:Skills Don’t Pay the Bills by reinhardt on Sunday November 25, 2012 @06:29AM (#4827903)
So from his whole rant about HR incompetency and almost calling them organisational cancer, the thing you took offence at was the only positive trait he attributed to them? The fact that you interpreted it as "reducing" says more about you than him.
Re:Skills Don’t Pay the Bills by white_devil on Sunday November 25, 2012 @06:23AM (#4827899)
the issue here is that they are human beings whom no one has the right to reduce as being mere eye-candy (which is particularly freaking sexist)

I'm sure women all around the world are extremely interested in Ryan Gosling's personality.

Re:Skills Don’t Pay the Bills by jrs235 on Sunday November 25, 2012 @08:47AM (#4828129)
Reduction to mere eye candy is not sexist. It's superficial. A guy saying a guy is mere eye candy wouldn't be sexist, same with a girl reducing a girl to eye candy. HR is often filled with attractive people.

His comment pertaining to not canning all of HR because they are the only cute GIRLS is sexist.

Re:Skills Don’t Pay the Bills by trevelyan on Sunday November 25, 2012 @07:11AM (#4827967)
Sounds like the sexism is more on the side of whoever hired ten male programmers and two female hr staff.
Re:Skills Don’t Pay the Bills by potatolicious on Sunday November 25, 2012 @12:11PM (#4828577)
The alternative would be more sexist. If you covered up everyone's names and fed their voice through a obfuscater you'd still end up with a similar ratio.

There are a lot more women in HR than men, and there are a lot more men in programming than women. There are many reasons why this is the case, many of which relate to sexism, but the fact that your overall result is gender-skewed is not in any way indicative of sexism in the hiring process.

Re:Skills Don’t Pay the Bills by xradionut on Sunday November 25, 2012 @09:10AM (#4828169)
It's obvious when I go to conferences and user group meetings that the majority of us programmers, admins and managers can spot most recuiters and HR folks at a glance. And it's offense to have clueless people in those postions, even more so when they are hired for looks.
Re:Skills Don’t Pay the Bills by bluesnowmonkey on Sunday November 25, 2012 @12:00PM (#4828545)
Diverse organizations perform better. Diversity of genders, ages, backgrounds. They are more balanced and have healthier decision-making processes. We've been tribal creatures for thousands of years and we've evolved to work best in mixed groups like that.

So if you're going to send a spaceship to Mars for a couple of years, you'd better mix some women in there, whether you consider it sexist or not. Likewise if you're going to put some people in a high-pressure startup for a couple of years, where they're spending almost all of their time and energy at the office, you'll probably have better and more consistent outcomes with a diverse group. That means both men and women, junior and senior, deep thinkers and fast movers.

Re:Skills Don’t Pay the Bills by skrebbel on Sunday November 25, 2012 @09:29AM (#4828218)
Time travel from the fifties, learn computers, and make an HN account. That's pretty damn cool if you ask me.
Re:Skills Don’t Pay the Bills by ucee054 on Sunday November 25, 2012 @07:12AM (#4827968)
they tend to be comprised of the only cute girls in the whole company

Why's that a reason not to fire the lot of them?

You have a harridan making your life miserable with stupid policies but she looks cute? You call that a good trade?

You know companies could employ competent ladies in place of those cute ladies.

Like a lady I knew who could write a whole network stack in assembler.

Re:Skills Don’t Pay the Bills by EliRivers on Sunday November 25, 2012 @01:16PM (#4828764)
"You have a harridan making your life miserable with stupid policies but she looks cute? You call that a good trade?"

It's the basis of my marriage. :)

Re:Skills Don’t Pay the Bills by cousin_it on Sunday November 25, 2012 @08:40AM (#4828118)
Would a good programmer (female or otherwise) want to work in HR instead of programming?
Re:Skills Don’t Pay the Bills by ucee054 on Sunday November 25, 2012 @08:32PM (#4829977)
I was implying hiring them as programmers and shrinking the HR dept.
Re:Skills Don’t Pay the Bills by achompas on Sunday November 25, 2012 @02:50AM (#4827611)
Agreed. Further, I personally think this is the issue at the core of the "data science shortage" right now.

"Data science" means many things to many people. Some shops want BI folks who can code. Others want people who can keep up in deep learning threads (like the one on HN's front page) and know about Hinton's work. Others still want HDFS badasses who can distinguish between Cascading and Cascalog (lol).

Shops classify all of these things as "data science" when they're really very different (respectively: Excel/scripting BI analyst; ML researcher with a focus on deep learning and neural networks; data infrastructure developer with broad exposure to MR frameworks)

This is stupid. I worried about checking off these boxes until I realized recruiters are doing the 1990s Java thing all over again. This time, though, the buzzwords are Hadoop, information retrieval, and Andrew Ng. I think it's best to ignore this, keep working hard, and grow your employment options.

Re:Skills Don’t Pay the Bills by Jach on Sunday November 25, 2012 @03:29AM (#4827679)
To add, I don't think it's usually so much that the buzzwords are useless things to learn or nebulous (though some probably are both), but it's that companies aren't willing to pay employees to learn the buzzwords on the job (or even figure out which subset is actually relevant to the job--YAGNI is a useful heuristic here). They'd rather instead complain about CS programs being inadequate. Then when CS programs half-assedly try to change into learn-this-software dev-mills, they get complaints from another side of the field that they're skipping out on important theoretical background that good programmers tend to have even if they don't use it much.

There are a lot of advertisements offering jobs only to people with "10+ years experience in X" (sometimes "X" hasn't even been a thing for that long), and assuming that means professional experience, that rules out almost everyone younger than 32. And for specific "X", it can rule out people even older if the "X" isn't what a recent graduate started getting their professional experience in right away. Some of those companies might also offer junior jobs with junior pay, but there are all these startups elsewhere offering higher-than-junior pay plus equity plus (depending on the size) a feeling of larger influence and control without the stress of running a company yourself.

I'm not sure I agree with you on ignoring buzzword-laden fields since there's usually a lot of money to be made, even if only in the short term. Though it's probably best not to greedily expand your employment options in the direction of the latest buzz.

Re:Skills Don’t Pay the Bills by eshvk on Sunday November 25, 2012 @03:24AM (#4827666)
I agree with you: However, I am unsure who is at fault here. There is a unique problem in that people don't genuinely know what to call the role they want to hire for and there is a worry among recruiters that the "wrong" or "unsexy" job title will put off potentially amazing candidates. E.g. In Linkedin, the data science position for the most part could be more accurately called a Machine Learning Engineer. There are other companies where the data science role could be called a Statistician (As in someone who has advanced degrees in Statistics but who for all they care can't write anything but SQL).

On the other hand, I have never ever found the requirements for a role to be nothing but mostly bullshit. So they don't really help you much. Your best bet if you are not going through a referral is to attempt to get to a phone screen where the Engineer/Data Scientist will be kind enough to spare some time at the end of the interview to tell you what on earth they are actually looking for. You could get lucky and learn just enough to terminate the interview process at this time. The worst situation is where you go there and realize that either a) You are not what they are looking for which is a half a day wasted or even worse b) They have not completely realized what they are looking for.

Me? I have made a decision that I will either apply for software engineering positions where I will maybe be one of the Machine Learning folks or apply to data science positions only if I know some one in the team who can explain to me what on earth that company is actually looking for.

Re:Skills Don’t Pay the Bills by ivany on Sunday November 25, 2012 @01:27AM (#4827481)
A similar problem is HR departments abusing the "knobs" on the position's requirements. For a software-based CRM company, they required something like 7 years of Java EE development experience for the lower level development positions, and 14+ for the team lead positions. How many 14 year Java developers are there? Furthermore, do you really need 14 years of experience in a particular language for this position? I think the HR desk is lamenting the lack of good applicants and turning up the "years of experience" knob, which is in all likelyhood counter-productive.
Re:Skills Don’t Pay the Bills by qq66 on Sunday November 25, 2012 @01:31AM (#4827485)
I've seen several job ads requiring "5+ years experience with Technology X" where Technology X is not yet 5 years old.
Re:Skills Don’t Pay the Bills by qq66 on Sunday November 25, 2012 @06:40AM (#4827922)
kenrikm, you have been hellbanned -- your posts are not visible but you're not informed of this. I hope you see this. I'm seriously considering leaving the HN community because of the frequency with which I see good contributors hellbanned.
Re:Skills Don’t Pay the Bills by lilsunnybee on Sunday November 25, 2012 @12:16PM (#4828600)
I'm ready to jump ship too. It's gotten ridiculous. I wonder if they keep track of which mods are hellbanning people. Is it just a few bad apples or is it systemic? I've seen so many thoughtful, but invisible posts lately that it makes me feel sort of sick.
Re:Skills Don’t Pay the Bills by nostrademons on Monday November 26, 2012 @12:10AM (#4830652)
It's not necessarily a person - I think PG has a machine-learning algorithm that's trained on the decisions of actual human mods, and then uses various features of the comment history to determine whether to hell-ban.
Re:Skills Don’t Pay the Bills by baltcode on Sunday November 25, 2012 @09:31AM (#4828220)
How did you see the hellbanned post?
Re:Skills Don’t Pay the Bills by plorkyeran on Sunday November 25, 2012 @09:55AM (#4828259)
Enable showdead in your profile.
Re:Skills Don’t Pay the Bills by Strshps1MoreTim on Sunday November 25, 2012 @08:54AM (#4828141)
Where to? What is a good discussion site similar to HN nowadays?
Re:Skills Don’t Pay the Bills by krapp on Sunday November 25, 2012 @09:05AM (#4828162)
You could make one. That's the easy part, though. Getting people to show up would be the hard part.
Re:Skills Don’t Pay the Bills by pebb on Sunday November 25, 2012 @03:51PM (#4829250)
Yeah, this is one of the most censored place around. It says a lot about the VC culture.
Re:Skills Don’t Pay the Bills by qq66 on Sunday November 25, 2012 @05:18PM (#4829476)
I don't actually mind censoring, but censoring someone without them knowing, and allowing them to contribute while thinking that their contributions are actually benefitting someone, is insane. In fact, just typing that out made me realize that I have to leave until they fix this issue.
Re:Skills Don’t Pay the Bills by nostrademons on Monday November 26, 2012 @12:13AM (#4830664)
That's how most large sites handle abuse & anti-spam protection. One of the cardinal rules of spam-defense is that you don't let spammers know that you've caught them, you just silently quarantine their spam. Otherwise, they'll adopt countermeasures and you're stuck in a rat race.
Re:Skills Don’t Pay the Bills by qq66 on Monday November 26, 2012 @02:26PM (#4833484)
If you're going to do that, you have to be 100% sure that a person is a spammer. One bad comment a year ago doesn't make someone a spammer.
Re:Skills Don’t Pay the Bills by nostrademons on Monday November 26, 2012 @06:04PM (#4834516)
I think PG's testing the hypothesis of "What if we don't have to be 100% sure? What if we probabilistically ban people based on comments that are likely to have no value? Will that result in a higher or lower community quality?"

Presumably the assumption is that some good people will be banned and leave, and some other good people will just leave out of sympathy, but it's better to have good people leave than have bad people enter the community. It's an interesting hypothesis, and HN has been going strong for 5+ years now with minimal moderation effort, though I have to admit that it seems to violate basic rules of fairness and empathy. Then again, a lot of businesses are built on being unfair to people.

Re:Skills Don’t Pay the Bills by qq66 on Tuesday November 27, 2012 @01:50AM (#4835989)
My argument is that you have some obligation to the person you are hellbanning, that a decent person can't just probabilistically waste a year of a stranger's life as part of an experiment on community quality.
Re:Skills Don’t Pay the Bills by kiba on Sunday November 25, 2012 @01:35AM (#4827495)
Don't forget that companies also discriminate against old people in favor of young people.

The result? They don't hire anybody despite a looooooooooong line of overqualified greybeards.

(I am young myself, too!)

Re:Skills Don’t Pay the Bills by eshvk on Sunday November 25, 2012 @03:43AM (#4827702)
I believe age discrimination is being split into two chunks:

1) Some people with a mistaken belief that correlation does imply causation think that just because some programmers have let their skillsets atrophy implies that one should stay away from older programmers.

2) Older people by virtue of experience, skillsets are pricing themselves out of the job market. I have an older friend who is a phenomenal hacker but doesn't like going into management. He found himself either being offered VP of Engg type roles which required way more management than he was willing to do or being given Engineering roles with way less money than he was prepared to accept. Also, once you get a family, the amount of leeway you have in accepting a tiny fraction of what you are worth in exchange for money and stocks becomes quite limited.

Re:Skills Don’t Pay the Bills by wyclif on Sunday November 25, 2012 @02:31AM (#4827578)
The problem is that age discrimination laws in the US aren't readily enforceable.
Re:Skills Don’t Pay the Bills by wyclif on Sunday November 25, 2012 @02:29AM (#4827573)
Yes, absolutely. I remember back when Java was only a few years old, it was common to see jobs where the company wanted 5-6 years of experience. Now, it could have been agency recruiters who had no idea what they were talking about, or it could have been coming from HR. But the result is the same: flagged for spam.
Re:Skills Don’t Pay the Bills by ishbits on Sunday November 25, 2012 @10:38AM (#4828336)
Sure wish I had a nickle for every time I've heard/read this.
Re:Skills Don’t Pay the Bills by continuations on Sunday November 25, 2012 @02:25AM (#4827566)
"Requirements:

- 25 years of HBase experience

- candidate must be 22 year old or younger"

Re:Skills Don’t Pay the Bills by kenrikm on Sunday November 25, 2012 @01:47AM (#4827518)
"Position requires 7 years of iOS Programming experience" ... the iOS SDK is only 4 years old.
Re:Skills Don’t Pay the Bills by logn on Sunday November 25, 2012 @02:37AM (#4827593)
Yes, it's similar. To explain the manufacturing situation in our terms, they're advertising for the equivalent of "Java programmer, 1 year of experience" and paying $10/hr. No one applies. Then there's a phony "skills gap". But also, no one wants to study to go into the field which actually creates a real skills gap.
Re:Skills Don’t Pay the Bills by nostrademons on Monday November 26, 2012 @12:16AM (#4830675)
Often times the absurdly specific skillset requirements are an H1B game. To get an H1B, you have to prove that no citizen is qualified for the position, so when companies find a foreign candidate they like, they'll put out a job ad with exactly the skillset that that candidate has, and then when nobody responds or all the candidates are unqualified, they can hire the person that they really wanted to hire in the first place.