Well, there are extreme cases that aren't representative, but "narrowing down" based on criteria that don't directly relate to the position is a poor strategy.
I find it interesting that there are many articles about what you should or should not do as a candidate (often contradictory), but little on what to avoid as an HR representative.
Why should HR people want to take the easy way out? Perhaps because it's an open-loop process - the hiring process seldom gets altered as a result of a bad hiring decision.
"You may call it "one-upmanship among writers", but the person in HR reviewing a resume may notice blatant errors also. And they are getting paid to get someone the least number of resumes possible, not translate and decode."
Funny, I thought the purpose was to hire the best possible candidate. If the goal is to "get someone the least number of resumes possible", then they should just submit the first 10 resumes on the pile. It's much more efficient and probably produces the same quality of candidates.
I always hear this kind of argument "we had skills and experience that were almost nonexistent in the US".
Since you were part of the program you should be able to spell-out in detail what relevant skills and/or experience you had that was supposed to be unavailable in the US. By "relevant", I mean skills directly used in your work.
Then we can see if US Slasdotters have or know someone who has those skills. That way we can get some indication if these claims are true or just BS.
There are already FSO (Free Space Optics) approaches for outdoor use that are superior to this new approach (see http://www.lightpointe.com/ for example).
As a developer who has written commercial applications for both Java and.NET platforms, I can assure you that.NET isn't a clone of Java.
Most languages/platforms are a particular mix of existing practices. There are very few brand-new ideas. The most original idea in Java is checked exceptions, and.NET doesn't include it.
"Microsoft goal for winning the browser war back in the late 90's was so they could have control of the standards and make the web their own so it would be useless to use the web without windows and Internet Explorer."
I don't think MS was stupid enough for that to be their real goal.
It depends if you think pissing off some of your customers is better than supporting IE6. I suspect that developers say "yes" and management says "no". Guess who gets the final word?
I suspect that this problem has been exaggerated on Slashdot because people here want to see IE6 die. Businesses that still use IE6 are probably satisfied with it or do exactly what you suggest if they have apps that depend on it.
Slashdot Mirror
Hey, feel free to use any criteria you want. It doesn't have to be logical.
Well, there are extreme cases that aren't representative, but "narrowing down" based on criteria that don't directly relate to the position is a poor strategy.
I find it interesting that there are many articles about what you should or should not do as a candidate (often contradictory), but little on what to avoid as an HR representative.
Why should HR people want to take the easy way out? Perhaps because it's an open-loop process - the hiring process seldom gets altered as a result of a bad hiring decision.
"You may call it "one-upmanship among writers", but the person in HR reviewing a resume may notice blatant errors also. And they are getting paid to get someone the least number of resumes possible, not translate and decode."
Funny, I thought the purpose was to hire the best possible candidate. If the goal is to "get someone the least number of resumes possible", then they should just submit the first 10 resumes on the pile. It's much more efficient and probably produces the same quality of candidates.
They used cheap engineering software and the moon-shot missed a mile,
The fellas in that rocket won't be back for quite a while.
I always hear this kind of argument "we had skills and experience that were almost nonexistent in the US".
Since you were part of the program you should be able to spell-out in detail what relevant skills and/or experience you had that was supposed to be unavailable in the US. By "relevant", I mean skills directly used in your work.
Then we can see if US Slasdotters have or know someone who has those skills. That way we can get some indication if these claims are true or just BS.
With over 20 years in this business if I'm a noob, what does that make you?
There are already FSO (Free Space Optics) approaches for outdoor use that are superior to this new approach (see http://www.lightpointe.com/ for example).
Do you recommend hiring other xenophobics?
"Java could run stand-alone, and it made apps portable to non-Win32."
I'm not sure what you mean by "stand-alone", given that a hefty JVM had to be installed on every platform.
This is only going to work in the small area that the laser can get to, so cables might be a better solution.
H1B has nothing to do with immigration. If H1B workers were citizens they wouldn't drive down salaries.
They weren't successful at all if the goal was to force people to use Windows.
As a developer who has written commercial applications for both Java and .NET platforms, I can assure you that .NET isn't a clone of Java.
Most languages/platforms are a particular mix of existing practices. There are very few brand-new ideas. The most original idea in Java is checked exceptions, and .NET doesn't include it.
"Microsoft goal for winning the browser war back in the late 90's was so they could have control of the standards and make the web their own so it would be useless to use the web without windows and Internet Explorer."
I don't think MS was stupid enough for that to be their real goal.
Part of the problem was that companies converted to browser-based apps without any real need to do so.
"Worst case, they fire you for complaining, and you get to tell an interviewer you got fired for raising the alarm on an inevitable failure."
Sure, I can just imagine telling my wife I got fired from my job but it was worth it because I helped save the world from IE6.
It depends if you think pissing off some of your customers is better than supporting IE6. I suspect that developers say "yes" and management says "no". Guess who gets the final word?
If it's true, it would be a huge mistake on Google's part. It would be far more convenient to start using Bing than downloading a new browser.
There's also potential antitrust issues here if IE6 were blocked from search.
I suspect that this problem has been exaggerated on Slashdot because people here want to see IE6 die. Businesses that still use IE6 are probably satisfied with it or do exactly what you suggest if they have apps that depend on it.
that IE6 users have a low participation percentage in Google services such as Docs.
For that reason it won't put much pressure on them to switch.
It sounds like your management if f***'d up. Of course, I don't know enough about the context in which these decisions were made to be sure.
If .NET (or C#) is just a clone of Java, I should be able to delete Java from my computer and still run Java apps. Have you tried it?
I don't think many Windows developers learned C# so they could "migrate their windows specific skillset to additional platforms".
C# is just the logical language to learn if you want to program for the .Net framework and you have a C/C++ background.
Does calling it the 2010 version mean that this a new version of an existing application? Or is this truly a brand new app?
If it is brand new, it isn't representative of Windows application developers.
Since when are liberals against vaccinations?