You cannot have more than 10 years of experience in Rails • Hacker News Board

Re: You cannot have more than 10 years of experience in Rails

#71

Post by HarryHirsch » Fri, Dec 26, 2014, 5:37 PM UTC

yummyfajitas wrote: post #67

HarryHirsch wrote: post #57

Earlier quoted context omitted.

You forgot to mention that the aim of H1B workers is to get a green card, and that for the EB1/EB2-NIV track, where the applicant files himself, a PhD degree is a near requirement. In the majority of cases it's the company that files for green card; if you change employer the process starts again all over. And there is a maximum of 5 years on H1B. It's not nearly as easy as you say. The environment is structured so t…

You are criticizing the GC process, not the h1b process. The h1b is to address a temporary worker shortage, not put people on a long term immigration track due to high skill. It would be great if we had such a track (beyond people of extreme talent), but we don't.

What temporary worker shortage? If there was one, there would be rising salaries, as we see in the North Dakota oil patch, but in IT wages are stagnant.

I'm criticizing US immigration, in general, temporary and permanent, because the present system benefits neither the majority of Americans nor the majority if immigrants. Large employers, though, benefit disproportionately.

Re: You cannot have more than 10 years of experience in Rails

#72

Post by lholden » Fri, Dec 26, 2014, 5:39 PM UTC

rabble wrote: post #36

I've got more than 10 years of rails experience. I started with Rails 0.5 in July 2004. So looking at the calendar we're at 10.5 years. There were only like 5 people including DHH when i joined the #rubyonrails irc channel. And on top of that i've done lots of other things in the rails world, like managing people since then. The thing is, rails has changed so much, i'm not sure how much value there is in that. If i w…

I'd be one of those folks in already #rubyonrails at the time. :)

Re: You cannot have more than 10 years of experience in Rails

#73

Post by kenrikm » Fri, Dec 26, 2014, 5:42 PM UTC

jetti wrote: post #44

Since there was no indication on the job ad that the position actually required 10 years of Rails experience, I'm going out on a limb and say that they just didn't want you/the author. From this brief article it seems that the author has a inflated ego, I mean I could never mess with an interviewer like that just because I know that people make mistakes. I think that this particular company didn't do anything wrong a…

Not related to this specific case since I generally think calling people out is bad form. However, I remember back in 2011 when looking at job postings for iOS Positions that "Required" 5+ years developing for "iOS" I could not help but chuckle that the only people that would have that would be the Apple developers who worked on it before it was released. 5+ years in Objective C sure, but at the time iOS was only 3 years old. Recently I've been seeing the same type of postings for "Swift" so it's important to keep in mind that just because the recruiter or first line interviewer does not know A from Z does not mean the organization as a whole is clueless. People make mistakes on job postings and in the case I think it's likely they just did not like him and that was the excuse they came up with to let him save face.

Re: You cannot have more than 10 years of experience in Rails

#74

Post by infinitone » Fri, Dec 26, 2014, 5:44 PM UTC

knappe wrote: post #3

Ruby the programming language wasn't developed by DHH. It was developed by Matz ( http://en.wikipedia.org/wiki/Ruby_%28programming_language%29 ). Second sentence, first paragraph. Also, the guy was replying to a Craigslist ad. I'm not really sure what he was expecting.

Yeah, that part made me cringe. Among other parts. This whole post is a mess tbh and makes it seem like the person is not fluent in English maybe?

Re: You cannot have more than 10 years of experience in Rails

#75

Post by infinitone » Fri, Dec 26, 2014, 5:51 PM UTC

anonfunction wrote: post #7

Earlier this year I saw a job listing for someone with 3+ years of experience with the swift programming language.

In theory it is possible, as I'm sure swift was in skunkworks at Apple for a good time before its public release.

Re: You cannot have more than 10 years of experience in Rails

#76

Post by towelguy » Fri, Dec 26, 2014, 7:02 PM UTC

rabble wrote: post #36

I've got more than 10 years of rails experience. I started with Rails 0.5 in July 2004. So looking at the calendar we're at 10.5 years. There were only like 5 people including DHH when i joined the #rubyonrails irc channel. And on top of that i've done lots of other things in the rails world, like managing people since then. The thing is, rails has changed so much, i'm not sure how much value there is in that. If i w…

What can a person with 10 years of experience in a framework know that someone with 2 doesn't?

Re: You cannot have more than 10 years of experience in Rails

#77

Post by bnjs » Fri, Dec 26, 2014, 7:38 PM UTC

Ra1d3n wrote: post #11

knappe wrote: post #3

Ruby the programming language wasn't developed by DHH. It was developed by Matz ( http://en.wikipedia.org/wiki/Ruby_%28programming_language%29 ). Second sentence, first paragraph. Also, the guy was replying to a Craigslist ad. I'm not really sure what he was expecting.

Well it's obvious to me that he meant Ruby on Rails.

But isn't the whole premise of the article that you're an idiot if you say things about languages/frameworks that aren't accurate?

Re: You cannot have more than 10 years of experience in Rails

#78

Post by cheald » Fri, Dec 26, 2014, 8:37 PM UTC

pekk wrote: post #70

rabble wrote: post #36

I've got more than 10 years of rails experience. I started with Rails 0.5 in July 2004. So looking at the calendar we're at 10.5 years. There were only like 5 people including DHH when i joined the #rubyonrails irc channel. And on top of that i've done lots of other things in the rails world, like managing people since then. The thing is, rails has changed so much, i'm not sure how much value there is in that. If i w…

"A language a year" is pretty pointless, especially if practice in any given language is not good.

You might be surprised. New languages can teach you quite a lot more than simply a new syntax - there are concepts that will be present and visible in a new language or stdlib that you might not have encountered before, and constant exposure to unfamiliar territory helps to keep you in constant learning mode.

The idea isn't that you abandon your existing languages every year. Nobody will be effective if they're always working exclusively in a language they've just started with, but you can take lessons learned in a new toy language and apply them to your broader work as a programmer, even if you never use that language again.

Re: You cannot have more than 10 years of experience in Rails

#79

Post by juliangregorian » Fri, Dec 26, 2014, 10:09 PM UTC

gaius wrote: post #9

if you are looking for a Senior PHP programmer or an algorithmic trading programmer let me know That is a very unusual mix of skills. Very unusual indeed.

Yes, an algo-trader in the financial hotbed of... Denver.

Not to mention senior PHP is junior anything else.

Re: You cannot have more than 10 years of experience in Rails

#80

Post by danieltillett » Fri, Dec 26, 2014, 10:54 PM UTC

pcl wrote: post #45

hga wrote: post #30

Earlier quoted context omitted.

Pay a fraction of a citizen or permanent resident's salary to a quasi-indentured servant, in that if you fire them it's iffy if they can find another H-1B gig before they have to leave the country. In the one case I observed first hand while at Lucent in 2001, an arguably more qualified and very smart Jamaican doing the same job as me was paid $48K (H-1B salaries have to be posted) while I was making $80K. He knew he…

In my experience, it's gone more like this: Find an awesome candidate for a position. He's on an H1B. Learn that he can only be hired into a position that can't be filled by a permanent resident, but can be filled by him. Create such a job description.

This is also my understanding of how these requirements come about. You have someone you want to hire, but you need to go through the pretence of trying and failing to hire.