3 ms·
Not being able to do something properly is not an excuse for doing it badly Yes it really is. I'm not a builder but if I had to shelter from weather I would ma
by jodrellblank 16y ago
Not being able to do something properly is not an excuse for doing it badly
Yes it really is. I'm not a builder but if I had to shelter from weather I would make a shelter. And my excuse for it being a low quality shelter is that I can't make a perfect one. And that would be better than nothing because at least I wouldn't die. Your idealism is idealistic but not helpful.
If iPhones couldn't read company email they wouldn't be as useful or as popular. If they could do so, but only by enforcing a horrible dual-personality where you had to manually switch between contexts they wouldn't sell as well or be as popular or useful. If they share data they are easier to use and more popular but not as easy to secure.
You say "not being able to do something properly" without addressing the fact that there is no accepted "proper" way to do it. They didn't ignore the proper way because they were lazy or stupid. Exchange email started on Windows Mobile devices for office use. That it has spread to consumer phones means the assumptions under which it was designed no longer hold.
and causing serious damage to someone as a result.
1) As far as we are told, no damage at all happened to her, she didn't even get lost after losing her navigation system.
2) We don't know that /serious/ damage happened to her.
3) The more serious the potential damage, the more important it was for her to have a backup of her important data and a backup of her important systems. There's no getting around this tradeoff.
4) The more serious the potential damage, the more important it is for her to understand what she is doing when making changes to her device and not blankly follow instructions to hook it up to things willy nilly.
Your second paragraph is a "person should be protected from all harm they don't understand by an all seeing overlord" argument, and it falls down where anyone else wants to do anything else or accept a different risk profile than uninformed easily panicked J. Bloggs.
- Silhouette 16y ago>> Not being able to do something properly is not an excuse for doing it badly > Yes it really is. I don't really know what I can say to this post. You have somehow turned this whole incident into the victim's fault, mitigating the consequences of the company IT staff's mistake into the victim's responsibility, and my argument that it is not reasonable for an employer to introduce such a drastic facility to destroy an employee's personal property without giving the employee fair warning into some unbounded "no-one should be responsible for anything" argument. We live in two different universes.
- jodrellblank 16y agoI haven't turned it ino that, I see it as that - apart from the fault bit. Nobody is at fault. The user didn't understand, the phone and email system isn't perfect, the IT staff made a mistake. These things happen. It doesn't need government legislation, lawyers and compensation. Shit happens. What do we do differently in future? We could try educating people about IT, but people don't care about IT. We could try legislation, but that costs time and money and makes life less pleasant. We could try not getting upset when everything isn't perfect and ideal. That helps. What makes you think the employee didn't get fair warning?
- Silhouette 16y ago> Nobody is at fault. ?! The corporate IT people screwed up and issued a data-loss command they apparently had neither reason nor authorisation to issue. Someone's personal property was completely wiped as a result. We don't know how much valuable personal data was on that phone, but it could have held e-mails, photographs, etc. They could have been important, have great sentimental value, even have been evidence in a legal action (e.g., photos taken after a road accident). In any case, this is clear cut negligence. The phone wipe might not have been deliberate, but the damage was done and it is absolutely clear who was at fault. > What makes you think the employee didn't get fair warning? Well, for one thing, this: "It was my account, in my name [and] I'd paid all the bills," Stanton says. "It didn't make any sense to me that somehow work could get through AT&T, who I thought controlled my phone, and could completely disable the phone and the account." Does that sound like the employee was properly informed to you?
- jodrellblank 16y agoWe don't know how much valuable personal data was on that phone, but it could have held e-mails, photographs, etc. They could have been important Then they should have a backup. In any case, this is clear cut negligence ?! Unless you want a world where every employee's every mouse click is monitored by another employee and everything takes two people, three times as long and costs four times as much in auditing you have to accept that accidents are not the same as negligence. Remote wipe is a web interface. Assuming the IT staff was supposed to wipe a different device, they either misread or misremembered the ID or misclicked (or were misinformed). One click. If you put your life on the line where one click can destroy it and you have no backup, and you still connect your device to systems you don't understand, you're running a huge risk and no amount of legislation will ever help you. Does that sound like the employee was properly informed to you? It sounds like someone who doesn't know how something works. They could well be someone who had it explained, agreed, then forgot. Or wasn't listening, or didn't care. Lots of people do that. Like the executives in your other comment who sat through a security presentation and then moments later showed they hadn't understood it at all on a conference call.