It's easier to have a job (at least, in a manufacturing sector) when you don't approve the Trans Pacific Partnership, or ask for the ability to fast track it. IT's also easier to have a job when your government imposes tariffs on nations like China, based on environmental and labor standards that are enforced locally, such that it makes no sense to offshore the manufacturing sector in the first place.
That said, I think that most inner city teens wouldn't have jobs, even if that discrepancy were corrected, since the value of the labor of an inner city teen is less than the current minimum wage. So you'd hire someone whose labor is equal to or more valuable than the minimum wage for those jobs instead, like an out of work adult.
The article is not about *stopping* riots.... it's about *predicting* them, so you know where to set up the news vans, and you know where to go to be on camera so you can demonstrate that you are a "community leader".
If you actually *stopped* the riots, it'd be a hell of a slow news day, and you'd have to run human interest stories about the baby ducks who've infested some guys swimming pool, or stories about cats.
How about "Emergency services personnel can't use a pulse oximetry device on your tattooed skin in order to save your life following a car accident"?
The device that's being interfered with is a pretty standard non-invasive pulse ox device that happens to be built into the watch.
Maybe the paramedics should use a standard finger pulse-ox meter instead of an iWatch.
The iWatch is not a certified medical device. I am specifically talking about standard pulse ox on someone who has done something like this to their fingers:
The real problem here is that IT is regarded as something like a janitorial service, rather than an integral business function.
You presume that Disney had only 125 total IT staff in the first place, and laid all of them off. From my reading of things, they laid off only the janitorial service type IT people, and kept the rest of them in house.
It's the color of LED that they use in the sensors. This has been a known issue since the FitBit hit the market with green LEDs a couple of years ago. Other smart watch vendors, like Samsung, learned the lesson and used other colors so have no problem. Apple, being Apple, seems to have decided that they were somehow "pioneers" in this market and didn't bother to do any actual research on what works for existing devices.
It's the color of LED that they use in the sensors. This has been a known issue since the FitBit hit the market with green LEDs a couple of years ago. Other smart watch vendors, like Samsung, learned the lesson and used other colors so have no problem.
If you tattoo your fingers, it will interfere with pulse ox devices. This is well known in the medical community. They generally work around it by using a different model and clipping it to your ear, scrotum, or some other place that doesn't have ink.
If you have inked yourself all over, they insert an optical catheter to take the measurements directly, or resort to semi-frequent blood draws.
This is what you get when you integrate an off-the shelf medical sensor into a wearable device not intended or certified to do medical things, and then don't have alternatives when someone has managed to screw with the ability of the sensor to operate by decorating themselves like a Christmas tree.
This is exactly my problem with Apple and many other product designers.
Yeah, most capacitive coupling (read as "nearly any touch sensitive device") doesn't work with gloves, unless they are specially made.
It also doesn't work with artificial limbs, which I think is probably a more important issue.
You can modify an artificial limb pretty trivially to make it work, just as you can modify a glove pretty trivially to make it work. I helped someone modify their Boch's artificial arms to allow them to use the touchpad on their IBM Thinkpad (also capacitively coupled). I declined to patent the modifications, and instead disclosed them into the public domain.
I hardly think "Can't use an Apple Watch" ranks very highly on the list of reasons not to get a tattoo since there's such an easy workaround -- don't buy an apple watch.
How about "Emergency services personnel can't use a pulse oximetry device on your tattooed skin in order to save your life following a car accident"?
The device that's being interfered with is a pretty standard non-invasive pulse ox device that happens to be built into the watch.
If you follow the second order links down to what Disney actually did, they outsourced their IT to a contracting agency.
When they did this, they laid off 125 full time employees in the process, and between three of the contracting agencies providing the services to replace them, there were apparent;y 65 H1-B applications in the last 3 years. Presumably, not all 65 went to Disney, because the contracting agencies contract services out to companies other than Disney. In fact, a vast number of dark data center porn and shopping sites are located in that area of the country, down by Los Angeles, where the majority of that kind of content is produced.
What this story is actually about, is complaining that the full time workers were replaced with contractors, some of whom were probably in the U.S. working for the contracting agencies on either H1 or L1 visas.
The summary is a gross misrepresentation of the facts here, and going with a contracting agency is a valid mechanism for ensuring "Just In Time" capability, without over-employing in order to handle upsurges in workloads. It's how janitorial and security services are handled (when you have a large company event, you have the contracted agencies put on more security people for the event itself, and added janitorial people post-event to clean up afterward.
That said, the usual route a decent company will follow when out-sourcing to a local agency, as opposed to off-shoring the work entirely, is to require that the contracting agency hire a certain percentage of the workers that are being laid off to replace them with contractors. This has the effect of ensuring continuity of service, providing a built-in mentoring capability to the contracting agency for the processes and procedures being contracted out, and in general providing continuity of employment for at least some of their existing staff.
It falls under the category of "Not Being Dickish About Switching Over To Contractors".
But the idea that they should not be switching over to contractors at all, for something like IT services, which are generally modular, replicable, and have uniformly applicable skill sets, if what you are spending your time doing is pulling wires, spinning up VMs, installing system software on replacement desktop/laptop machines, and so on, is patently absurd. These are "cog jobs", where any sufficiently skilled cog can replace any other sufficiently skilled cog in the machine, and you probably won't lose a marching step over the replacement.
That, and surge scalability, make them rather ideal for out-sourcing.
Frankly, I'm surprised companies like RackSpace are renting out their IT people, rather than forcing everyone to live on RackSpace racks; it's a pretty ideal scenario for them, in terms of profit per employee, and gives them buffer for their own internal surge scalability issues. They get borrowable capacity, and other people pay to maintain that capacity at a certain level.
Add the fact that a lot of deployment is on OpenStack with standard deployment tools, no matter if you're working on your cloud or working on someone else's cloud: all the tools are the same, so all the skills are pretty much transferrable.
This is kind of what happens when you sufficiently commoditize an industry through standardization.
With out them we can be replaced by contractors and it's the contract firm that is the one useing the H1B's
People say this, but if you work in the context of a union, you might as work for a contracting agency, and skip a step. For most U.S. states, being in a union is a pretty useless activity, for everyone but the union itself, since most IT jobs are in "at will" states. Do not think that this is not *why* most of those jobs are in those states.
I have *never* sen a successful unionization of a programming shop; they fall apart, and are reformed almost immediately with non-union employees.
So like the cops... it shows up only after the crime has been committed, and only protects some of the population (Google passwords) and not the rest of the population (e.g. your banking password isn't protected, because it's not a Google site).
The Dragon launch may be rescheduled... to avoid space debris. the orbit the craft was in ended up too high; that junks going to be up there a loooooong time.
"Smith hopes, of course, that his plan will accelerate IBM's internal development, and make it more competitive against not only its tech-giant competition, but also the host of startups working in common fields such as artificial intelligence."
Well, that's not going to happen.
I was at IBM lin the very early 2000's. They were already using agile development methodology, and using Skype as an incontrollable interrupt source, rather than Lotus Notes is unlikely to do much beyond making executives feel better that you are always reachable so as to be a le to conveniently move the goal posts out from under you.
Also IBM's internal development model is to polish customer facing systems, which tend to be human-centric, while internal systems tend to be held together with spit and bailing wire, while doing the absolute minimum to get them to work, and they tend to be very labor intensive for the humans who have to end up using them. I really don't see this ending up where he wants things to end up.
Example: there were twenty three separate systems that someone had to drive the process through to get an IBM Web Connections account up and running, and a lot of that work had to do with copy/paste between browser Windows, TN3270 terminal Windows, sending email requests via Lotus Notes, and so on. Once these systems were up and running, I did an analysis of all the interactions and steps required, with an aim to reducing the overall complexity and change of error. Management was not interested: once something is barely working well enough to get the job done, there's zero interest in the process of working on the process; among other things, it means less job security.
I don't see this changing wildly, given the reward systems in place for employees have not changed significantly, according to people I know who still work there. The entire business model for IBM Global Services is based on giving people what they ask for, as opposed to what they actually want/need, and then iterating the process in an "Agile" fashion to suck as much money out of the customer as possible. This was true of internal IT systems as much as it was for customer facing contracts.
Once again: I really don't see this ending up where he wants things to end up.
Here, on/. , we find people who think you can leave your Windows machine running 24x7 with not a care in the world. As if it would never abend, never update and reboot, nor would any badly behaved app or driver decide to crash and take the kernel with it.
Just use Windows XP. I hear it no longer updates and reboots on you.
Well, if it walks like a taxicab and talks like a taxicab, how is it not a taxicab? Because you signal it with a hep and cool app instead of making a phone call?
No $300,000 buy-in for a medallion in San Francisco or Chicago?
They actually show up when they're supposed to, rather than taking whoever flags them down instead on their way to you?
They don't blow you off and lie to the dispatcher about it?
Let's see... how else are Uber and Lyft different from taxis?
Modern cars instead of a 20 year old Ford Crown Victoria or Dodge Diplomat?
I would be pretty shocked if you are even remotely on the right track.
I did over 50 interviews of technical candidates while at Google, and 6 of them were phone screens.
One of them tried this on me, so it definitely happens. Two of them tried the "look things up on the Internet to answer the question" trick.
Personally, I would have had him drive the hour and a half from Boynton Beach to the Miami MarCom office, and interview from there. I don't recruit directly since my pre-Google/pre-Apple/Pre-IBM days, but if you are acting as a recruiter, one of the best gauges of a candidates personality is the front desk person's opinion of them. I can't see a recruiter passing on that information.
Shields should have gone up from the they-contact-you-because-you're-desirable-then-they-phone-screen moment. If they want you, they'll call you in, and if they *really* want you, they'll fly you to Mountain View to get a full team on your interview.
PS: I was 5 minutes late to exactly one of them because the bike I was riding to the building broke down. It would be interesting to hear an explanation of why the recruiter was not on the line with the person at the appointed time, and telling them of the schedule change and asking if it was OK with the candidate. For the on-site I was late for, the last interviewer stayed with the candidate until I got there. At a full 10 minutes of no-show I would have been substituted.
Gatekeeper also isn't "all MacOS X security". There's separate malware detection, and in order to do much of anything the user has to enter their computer account password.
It's a minor part of OS X security, mostly designed to keep casual users from installing stuff outside the apple store.
Yes.
There's also Mandatory Access Controls (MAC Framework) in the kernel itself, and there's BSM secure auditing in the kernel itself, and there's discretionary access controls, such as standard UNIX permissions, and there's POSIX.1e draft (it was never ratified as a standard) ACLs, and then there's whatever malware detection or antivirus protection you've jammed into the kernel as a MAC module via a KEXT, and in the absence of any access controls whatsoever, it's default deny, and then there's code signing, and encrypted pages within executables.
They didn't bypass any of that, and they wouldn't really be able to, even if they were root, because you can't get the Mac port for the kernel virtual address space without jumping through a massive number of hoops (which is why jailbreaking phones is non-trivial, and everyone uses script kiddy tools to do it, instead of jailbreaking from scratch).
And yeah, it's pretty stupid that Gatekeeper or anything else would be running as root and thus be exploitable with the escalated privilege available at install time, since it'd be pretty easy to just have it run as a role-based account, and have the kernel's cooperation, after cryptographic verification of the developer keys at the kernel level. But that doesn't let you bypass "All OS X Security": getting root doesn't really get you nearly 1/10th of the security bypassed (less, if you've installed third party anti-malware KEXTs that refuse to be unloaded except in single user mode during boot as part of an uninstall script, and are therefore always active).
They clearly do not understand the concept of "security in depth".
Personally, I don't think he was talking to Google; at least not directly.
He got called by a recruiter, supposedly for Google, who set up a phone interview Looking for C/C++ and Java. Fine. There's an outside chance of Java, either as an Android App developer, or for some server back end crap at a company they purchased. It's unlikely, but it's possible (in 2011, they hired people to work at Google, and then groups decided to offer them, and then you got a choice of usually one of 3 groups... you didn't know what you'd be working on at interview time, and there was no such thing as "hiring for position" unless you were net.famous).
Then he didn't get sent a Google Docs link by the interviewer. You are *always* sent a Google Docs link by the interviewer, unless you are in a city/area where Google has a facility, then you are instead brought in to use the video conferencing at the Google location.
Then he got an interviewer who barely spoke English, and wouldn't take him off speakerphone. That never happens at Google.
The interviewer was 10 minutes late to the call.
Frankly, sir, IMHO, you got played.
You just got man-in-the-middled by an Indian or other foreign person who wanted a job at Google, and got you to ghost his or her phone interview for them, with the help of a "recruiter"/"interviewer" who had you on lousy speakerphone so that they could relay your answers directly via a cell phone to the person Google was actually talking to.
Yes, this happens.
No, savvy technical people generally don't fall for it, because they get an email from Google telling you the schedule, there's a Google Doc URL sent out with an @google.com address, and if you look at the email headers in the email of the schedule, you'll see that they are probably forged, assuming you got one at all.
Congratulations on being played, Mr. Robert Heath.
Slashdot Mirror
They tend to be rather quickly destroyed by criminals so that there's no admissible record of their criminal activities.
It's harder to riot when you have a job.
It's easier to have a job (at least, in a manufacturing sector) when you don't approve the Trans Pacific Partnership, or ask for the ability to fast track it. IT's also easier to have a job when your government imposes tariffs on nations like China, based on environmental and labor standards that are enforced locally, such that it makes no sense to offshore the manufacturing sector in the first place.
That said, I think that most inner city teens wouldn't have jobs, even if that discrepancy were corrected, since the value of the labor of an inner city teen is less than the current minimum wage. So you'd hire someone whose labor is equal to or more valuable than the minimum wage for those jobs instead, like an out of work adult.
The article is not about *stopping* riots.... it's about *predicting* them, so you know where to set up the news vans, and you know where to go to be on camera so you can demonstrate that you are a "community leader".
If you actually *stopped* the riots, it'd be a hell of a slow news day, and you'd have to run human interest stories about the baby ducks who've infested some guys swimming pool, or stories about cats.
How about "Emergency services personnel can't use a pulse oximetry device on your tattooed skin in order to save your life following a car accident"?
Don't most pulse oximeters work by shining a certain frequency of light through fingernails?
No. They shine through the pad of the fingertip to the blood vessels there. Otherwise they would not work on people wearing nail polish.
How about "Emergency services personnel can't use a pulse oximetry device on your tattooed skin in order to save your life following a car accident"?
The device that's being interfered with is a pretty standard non-invasive pulse ox device that happens to be built into the watch.
Maybe the paramedics should use a standard finger pulse-ox meter instead of an iWatch.
The iWatch is not a certified medical device. I am specifically talking about standard pulse ox on someone who has done something like this to their fingers:
http://blog-cdn.tattoodo.com/w...
If people are going to tattoo their wrists and faces, they are sure as hell going to do their fingers.
The real problem here is that IT is regarded as something like a janitorial service, rather than an integral business function.
You presume that Disney had only 125 total IT staff in the first place, and laid all of them off. From my reading of things, they laid off only the janitorial service type IT people, and kept the rest of them in house.
It's the color of LED that they use in the sensors. This has been a known issue since the FitBit hit the market with green LEDs a couple of years ago. Other smart watch vendors, like Samsung, learned the lesson and used other colors so have no problem. Apple, being Apple, seems to have decided that they were somehow "pioneers" in this market and didn't bother to do any actual research on what works for existing devices.
It's the color of LED that they use in the sensors. This has been a known issue since the FitBit hit the market with green LEDs a couple of years ago. Other smart watch vendors, like Samsung, learned the lesson and used other colors so have no problem.
If you tattoo your fingers, it will interfere with pulse ox devices. This is well known in the medical community. They generally work around it by using a different model and clipping it to your ear, scrotum, or some other place that doesn't have ink.
If you have inked yourself all over, they insert an optical catheter to take the measurements directly, or resort to semi-frequent blood draws.
This is what you get when you integrate an off-the shelf medical sensor into a wearable device not intended or certified to do medical things, and then don't have alternatives when someone has managed to screw with the ability of the sensor to operate by decorating themselves like a Christmas tree.
This is exactly my problem with Apple and many other product designers.
Yeah, most capacitive coupling (read as "nearly any touch sensitive device") doesn't work with gloves, unless they are specially made.
It also doesn't work with artificial limbs, which I think is probably a more important issue.
You can modify an artificial limb pretty trivially to make it work, just as you can modify a glove pretty trivially to make it work. I helped someone modify their Boch's artificial arms to allow them to use the touchpad on their IBM Thinkpad (also capacitively coupled). I declined to patent the modifications, and instead disclosed them into the public domain.
I hardly think "Can't use an Apple Watch" ranks very highly on the list of reasons not to get a tattoo since there's such an easy workaround -- don't buy an apple watch.
How about "Emergency services personnel can't use a pulse oximetry device on your tattooed skin in order to save your life following a car accident"?
The device that's being interfered with is a pretty standard non-invasive pulse ox device that happens to be built into the watch.
Take them to court over what? It's not like Microsoft hasn't been perfectly open about support ending last April.
At a guess... not building a secure product not requiring updating in the first place?
I agree.
If you follow the second order links down to what Disney actually did, they outsourced their IT to a contracting agency.
When they did this, they laid off 125 full time employees in the process, and between three of the contracting agencies providing the services to replace them, there were apparent;y 65 H1-B applications in the last 3 years. Presumably, not all 65 went to Disney, because the contracting agencies contract services out to companies other than Disney. In fact, a vast number of dark data center porn and shopping sites are located in that area of the country, down by Los Angeles, where the majority of that kind of content is produced.
What this story is actually about, is complaining that the full time workers were replaced with contractors, some of whom were probably in the U.S. working for the contracting agencies on either H1 or L1 visas.
The summary is a gross misrepresentation of the facts here, and going with a contracting agency is a valid mechanism for ensuring "Just In Time" capability, without over-employing in order to handle upsurges in workloads. It's how janitorial and security services are handled (when you have a large company event, you have the contracted agencies put on more security people for the event itself, and added janitorial people post-event to clean up afterward.
That said, the usual route a decent company will follow when out-sourcing to a local agency, as opposed to off-shoring the work entirely, is to require that the contracting agency hire a certain percentage of the workers that are being laid off to replace them with contractors. This has the effect of ensuring continuity of service, providing a built-in mentoring capability to the contracting agency for the processes and procedures being contracted out, and in general providing continuity of employment for at least some of their existing staff.
It falls under the category of "Not Being Dickish About Switching Over To Contractors".
But the idea that they should not be switching over to contractors at all, for something like IT services, which are generally modular, replicable, and have uniformly applicable skill sets, if what you are spending your time doing is pulling wires, spinning up VMs, installing system software on replacement desktop/laptop machines, and so on, is patently absurd. These are "cog jobs", where any sufficiently skilled cog can replace any other sufficiently skilled cog in the machine, and you probably won't lose a marching step over the replacement.
That, and surge scalability, make them rather ideal for out-sourcing.
Frankly, I'm surprised companies like RackSpace are renting out their IT people, rather than forcing everyone to live on RackSpace racks; it's a pretty ideal scenario for them, in terms of profit per employee, and gives them buffer for their own internal surge scalability issues. They get borrowable capacity, and other people pay to maintain that capacity at a certain level.
Add the fact that a lot of deployment is on OpenStack with standard deployment tools, no matter if you're working on your cloud or working on someone else's cloud: all the tools are the same, so all the skills are pretty much transferrable.
This is kind of what happens when you sufficiently commoditize an industry through standardization.
With out them we can be replaced by contractors and it's the contract firm that is the one useing the H1B's
People say this, but if you work in the context of a union, you might as work for a contracting agency, and skip a step. For most U.S. states, being in a union is a pretty useless activity, for everyone but the union itself, since most IT jobs are in "at will" states. Do not think that this is not *why* most of those jobs are in those states.
I have *never* sen a successful unionization of a programming shop; they fall apart, and are reformed almost immediately with non-union employees.
So like the cops... it shows up only after the crime has been committed, and only protects some of the population (Google passwords) and not the rest of the population (e.g. your banking password isn't protected, because it's not a Google site).
Seems slightly less than useful.
The Dragon launch may be rescheduled... to avoid space debris. the orbit the craft was in ended up too high; that junks going to be up there a loooooong time.
You have to learn to walk before you can run.
It's a trite aphorism.
I'd point out that in order to run a marathon, you have to train for a marathon. Walking is not a very suitable means of doing this.
"Smith hopes, of course, that his plan will accelerate IBM's internal development, and make it more competitive against not only its tech-giant competition, but also the host of startups working in common fields such as artificial intelligence."
Well, that's not going to happen.
I was at IBM lin the very early 2000's. They were already using agile development methodology, and using Skype as an incontrollable interrupt source, rather than Lotus Notes is unlikely to do much beyond making executives feel better that you are always reachable so as to be a le to conveniently move the goal posts out from under you.
Also IBM's internal development model is to polish customer facing systems, which tend to be human-centric, while internal systems tend to be held together with spit and bailing wire, while doing the absolute minimum to get them to work, and they tend to be very labor intensive for the humans who have to end up using them. I really don't see this ending up where he wants things to end up.
Example: there were twenty three separate systems that someone had to drive the process through to get an IBM Web Connections account up and running, and a lot of that work had to do with copy/paste between browser Windows, TN3270 terminal Windows, sending email requests via Lotus Notes, and so on. Once these systems were up and running, I did an analysis of all the interactions and steps required, with an aim to reducing the overall complexity and change of error. Management was not interested: once something is barely working well enough to get the job done, there's zero interest in the process of working on the process; among other things, it means less job security.
I don't see this changing wildly, given the reward systems in place for employees have not changed significantly, according to people I know who still work there. The entire business model for IBM Global Services is based on giving people what they ask for, as opposed to what they actually want/need, and then iterating the process in an "Agile" fashion to suck as much money out of the customer as possible. This was true of internal IT systems as much as it was for customer facing contracts.
Once again: I really don't see this ending up where he wants things to end up.
Here, on /. , we find people who think you can leave your Windows machine running 24x7 with not a care in the world. As if it would never abend, never update and reboot, nor would any badly behaved app or driver decide to crash and take the kernel with it.
Just use Windows XP. I hear it no longer updates and reboots on you.
Just read and memorize the manuals so that it's not an issue.
Well, if it walks like a taxicab and talks like a taxicab, how is it not a taxicab? Because you signal it with a hep and cool app instead of making a phone call?
No $300,000 buy-in for a medallion in San Francisco or Chicago?
They actually show up when they're supposed to, rather than taking whoever flags them down instead on their way to you?
They don't blow you off and lie to the dispatcher about it?
Let's see... how else are Uber and Lyft different from taxis?
Modern cars instead of a 20 year old Ford Crown Victoria or Dodge Diplomat?
Lack of vomit smell/stale cigarette smoke smell?
I would be pretty shocked if you are even remotely on the right track.
I did over 50 interviews of technical candidates while at Google, and 6 of them were phone screens.
One of them tried this on me, so it definitely happens. Two of them tried the "look things up on the Internet to answer the question" trick.
Personally, I would have had him drive the hour and a half from Boynton Beach to the Miami MarCom office, and interview from there. I don't recruit directly since my pre-Google/pre-Apple/Pre-IBM days, but if you are acting as a recruiter, one of the best gauges of a candidates personality is the front desk person's opinion of them. I can't see a recruiter passing on that information.
Shields should have gone up from the they-contact-you-because-you're-desirable-then-they-phone-screen moment. If they want you, they'll call you in, and if they *really* want you, they'll fly you to Mountain View to get a full team on your interview.
PS: I was 5 minutes late to exactly one of them because the bike I was riding to the building broke down. It would be interesting to hear an explanation of why the recruiter was not on the line with the person at the appointed time, and telling them of the schedule change and asking if it was OK with the candidate. For the on-site I was late for, the last interviewer stayed with the candidate until I got there. At a full 10 minutes of no-show I would have been substituted.
"... that aims to automatically suggest cancer diagnoses..." even if you don't actually have cancer.
Well, it's been estimated that the number programmers doubles about every 5 years.
That was a misprint; that's not the actual number of them, as individuals, that's by weight.
Gatekeeper also isn't "all MacOS X security". There's separate malware detection, and in order to do much of anything the user has to enter their computer account password.
It's a minor part of OS X security, mostly designed to keep casual users from installing stuff outside the apple store.
Yes.
There's also Mandatory Access Controls (MAC Framework) in the kernel itself, and there's BSM secure auditing in the kernel itself, and there's discretionary access controls, such as standard UNIX permissions, and there's POSIX.1e draft (it was never ratified as a standard) ACLs, and then there's whatever malware detection or antivirus protection you've jammed into the kernel as a MAC module via a KEXT, and in the absence of any access controls whatsoever, it's default deny, and then there's code signing, and encrypted pages within executables.
They didn't bypass any of that, and they wouldn't really be able to, even if they were root, because you can't get the Mac port for the kernel virtual address space without jumping through a massive number of hoops (which is why jailbreaking phones is non-trivial, and everyone uses script kiddy tools to do it, instead of jailbreaking from scratch).
And yeah, it's pretty stupid that Gatekeeper or anything else would be running as root and thus be exploitable with the escalated privilege available at install time, since it'd be pretty easy to just have it run as a role-based account, and have the kernel's cooperation, after cryptographic verification of the developer keys at the kernel level. But that doesn't let you bypass "All OS X Security": getting root doesn't really get you nearly 1/10th of the security bypassed (less, if you've installed third party anti-malware KEXTs that refuse to be unloaded except in single user mode during boot as part of an uninstall script, and are therefore always active).
They clearly do not understand the concept of "security in depth".
Personally, I don't think he was talking to Google; at least not directly.
He got called by a recruiter, supposedly for Google, who set up a phone interview Looking for C/C++ and Java. Fine. There's an outside chance of Java, either as an Android App developer, or for some server back end crap at a company they purchased. It's unlikely, but it's possible (in 2011, they hired people to work at Google, and then groups decided to offer them, and then you got a choice of usually one of 3 groups... you didn't know what you'd be working on at interview time, and there was no such thing as "hiring for position" unless you were net.famous).
Then he didn't get sent a Google Docs link by the interviewer. You are *always* sent a Google Docs link by the interviewer, unless you are in a city/area where Google has a facility, then you are instead brought in to use the video conferencing at the Google location.
Then he got an interviewer who barely spoke English, and wouldn't take him off speakerphone. That never happens at Google.
The interviewer was 10 minutes late to the call.
Frankly, sir, IMHO, you got played.
You just got man-in-the-middled by an Indian or other foreign person who wanted a job at Google, and got you to ghost his or her phone interview for them, with the help of a "recruiter"/"interviewer" who had you on lousy speakerphone so that they could relay your answers directly via a cell phone to the person Google was actually talking to.
Yes, this happens.
No, savvy technical people generally don't fall for it, because they get an email from Google telling you the schedule, there's a Google Doc URL sent out with an @google.com address, and if you look at the email headers in the email of the schedule, you'll see that they are probably forged, assuming you got one at all.
Congratulations on being played, Mr. Robert Heath.
That explains your "creative" typing patterns.
It's actually the meth.