Sorry, but I think you might have missed the sarcasm that I was aiming for...

But I will add that I no longer build my own PCs. Not because I can't, but mostly because I had a hard time settling for the low-end, cheap parts (if I'm going to build a rig, it's going to be the hottest rig around, at least for the next week or so). Buying OTS ended up saving me a lot of time and money. I usually go w/ HP's, bump up the memory and otherwise go w/ the system as-is. They may pick up cheaper parts, but for the most part I've had nothing but success getting linux running on them.

Yep, just like programming Windows in C is so very similar to programming windows in C++, PowerBuilder, Java, Assembly, ... (it's just different languages, but it is on the same platform).

When I get my new PCs, the first thing I do is wipe them clean and reinstall windows.

I'm just careful when I grab the disk labeled "Ubuntu" because I know that version of windows doesn't come with all of the problems the OP identified.

Here's why you shouldn't learn Obj-C first:

While you're busy learning obj-C, the rest of the ios developers will be learning Swift. In 5 years, by the time Apple has retired Obj-C, you'll be left with another out of date skillset. In 5 years companies will be looking for Swift developers, and you won't be ready, and you will once again find yourself behind everyone else.

Heck, maybe that's why these fools are telling you to learn Obj-C; they're looking to reduce competition on the Swift jobs that they're already working towards.

Instead, like I said, don't listen to these folks that don't know what they're talking about. You want to position yourself ahead of the curve, mastering Swift now while they're falling behind the 8 ball with their old obj-C skills. By the time you feel comfortable with Swift, you will be well ahead of the curve and companies will be wanting you on their team, not these obj-C folks.

Don't listen to these ass clowns saying "Go with Obj-C". If they had any clue they would know that introducing Swift was the first step towards obsoleting Obj-C.

Assuming you're not learning this language to obsolete yourself, then you definitely want to stick with Swift.

This is a new government program. They do want to kill you, but they really want to know what you have first, just in case it is really damaging. By giving them your stuff, they can make an informed decision whether to murder you right away or possibly (although not likely) hold off for awhile.

You typed "I love Dice".

we're self linking now?

We need janitors, security guards, cafeteria workers, secretaries, mail room personnel, typists, clerks, ... The critical thinking that the LA degrees bring ensures they understand that they need their jobs to pay off their student loans, so they're really more like indentured servants than employees.

bullshit.

You, the inventor, sell your soul for 17k. IV doesn't turn your idea into a product. Instead they look at what other smart guys and deep pocket companies are creating, claim a murkey relation to the patent they purchased but did nothing about, then try to sue them for millions - some will fight, some will settle, some will lose, but in the end IV makes well more than 17k w/o doing a thing.

Before you go defending IV or any other patent troll, do the following calculation - Divide the number of lawsuits by the number of real products for sale. Any result greater than 1 does not deserve your defense, and the result you get for IV is totally indefensible.

They seem to think the decline of support behind YUI is somewhat based on node and other newer frameworks.

Sure, I know what node is. I also know the other 12 projects they did mention (and jQuery and others that they didn't). I also know that they wouldn't have accepted the submission if I had listed all 14...

I'm not using beta, cuz I don't want to see live videos in the news feed, in case anyone @slashdot/@dice even cares...

manages the relationships between the company and external vendors (benefits such as health, dental, vision, 401k, they all have different sources and require their own upkeep), is the proxy between the employee and those vendors, oversees the process of hiring and firing (to ensure no laws or rights are violated), etc.

It's all management stuff, but when an exec says "Hey, we're using ziprecruiter because I played golf with a guy that just loved It", she's stuck with it until she can demonstrate that it is not all that it's cracked up to be.

So my wife is in HR, so let me explain why they use these kinds of systems...

First, for any particular job opening managers are putting pressure on to get the ad in the paper, get the notice up on every job posting board there is, get word out to employees, headhunters, etc. They want their position(s) filled as soon as possible, many times they feel like if they don't get the job filled right away some bean counter might realize that the job isn't really necessary and lots of money can be saved by eliminating the position.

Now with all of those postings someone has to create the actual ad and job description. This is pretty tough since managers will tend to ask for specifics (must know how to use the 1980 version of drill press 123), but this has to be translated into something that is a little more open to receiving viable candidates. There's also the challenge of getting all of the requirements from the managers so the posting is complete.

Then the fun begins. Headhunters want to provide 'screened' candidates (which end up being a result of a query on some database they have that kicks back a list of folks that may or may not have all of the skills necessary). There's also a lot of cruft and spam that come in for the job posting (lots of job bots out there), and there's also people who are not really qualified for the job applying anyway cuz they're looking to make that next big career move. And with the glut of unemployed out there, you get folks who are out of the area, folks who are overqualified, underqualified, etc. who all just need a job to keep their house, car, kids, dignity, whatever...

Many of these sites that are used are not really picked or coded by HR in any way, they're generic sites (perhaps themed, but generic none the less) like zip recruiter (POS, if you ask me). These sites love applicants and resumes etc., but they also employ some sort of "qualified applicant" filter so that all applicants don't ever get to HR. And no, HR does not usually pick these kinds of sites, they'll get picked by business folks who are looking to save money in the organization and get convinced that zip recruiter will help them do that.

Another thing companies are using are personality tests. They too are sold to executives as ways to automatically filter out 'incompatible' people. In some cases they may work, but in reality they can typically be gamed to get you through. Surprisingly though, many folks don't know they can be gamed and answer them honestly; unfortunately for them, the execs tweak the test so much that only supermen get through (i.e. like a salesman who can sell ice cubes to eskimos kind of perfect candidates). Many times these filters end up being over-aggressive and end up blocking what may otherwise be good potential candidates had they known how to game the tests.

As far as the uploading resume goes, well those end up going to the hiring manager (because they want resumes, not forms or reports). The forms, however, are necessary for all of the computer filters, etc. to weed out unqualified applicants. They have no real HR function outside of that (although it is easier to work off of reports of candidates).

Finally, just as it is in IT, if you want to screw something up really bad in HR just get the executives involved. They're the ones that mess things up over there just as much as they do in IT...