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.

No. They shine through the pad of the fingertip to the blood vessels there. Otherwise they would not work on people wearing nail polish.

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.

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.

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.

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.

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.

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.

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.

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.

Just use Windows XP. I hear it no longer updates and reboots on you.