Yeah, I guess I should be clear. I absolutely believe that most failures in healthcare are systems issues. I would never want a nurse to be prosecuted for making a mistake. I just read this story as "a nurse deliberately bypassed a safety feature, resulting in the death of a patient." You're absolutely right that even then, it could be a training issue, or a workload issue, or a combination of factors. I shouldn't be too quick to judge.
In many cases it comes down to the resourcefulness of the nurse. I have heard of at least one case of a nurse who gave an enteral feeding intravenously. The connections were incompatible. Her solution was to attach the two ends together and keep them in place with surgical tape.
I hope she was fired and prosecuted, but somehow I suspect otherwise.
So you oppose patents, then? Or do you like mommy-granted monopolies, and just start crying when the other children try to get your monopoly taken away?:-P
Blame CmdrTaco for that -- the document and the summary both state it's not the real IETF. (It was submitted to the RFC editor for consideration as the April Fools' RFC, but rejected.)
I currently use SPF, and am thinking about dropping it. It causes me a massive pain in my ass every time some dumbass with a misconfigured forwarder doesn't understand SPF or SRS, and tries to blame me for the fact that they can't receive email from me. There just aren't enough large sites sending SPF-enabled mail for misconfigured receiving sites to realize they're doin' it wrong.
You should write up your story in more detail (e.g. how you kept your cool and managed to analogize three more jurors into agreeing with you, without getting kicked off the jury) and post it somewhere. FIJA would certainly publish it for you, and it would be a valuable resource.
What this guy doesn't get is that most so-called 'libertarians' don't really like freedom -- they just hate anything that looks like cooperation or collectivism. It doesn't matter whether it's voluntary. So while I applaud his principled stance, he's going to have trouble getting anybody to listen.
Unless any of this is documented anywhere that _I_ the consumer can read it, it's all useless bullshit distinctions to me. I just want to know whether my data will work. All your factors are irrelevant to me unless it's documented somewhere what they are, so I can control for them. Otherwise the article's approach of testing randomly is a better and more realistic approximation of the conditions I will actually _get_.
Disclaimer: I have T-Mobile, so all the information in the article is useless to me anyway.:-P
Hmm, according to the docs that's automatically set on OSX. And anyway, I'm not sure what Unison could usefully do besides fail out -- if I have 'A' and 'a' on the Linux end, and they're different files, what should it deposit on the Mac end? Ignoring case does't help make that decision. If it just picked one at random, that'd be worse.
Currently? Just unison -quiet, running from cron. (I have it wrapped in a script that does locking, since Unison doesn't seem to lock against itself reliably, for reasons I don't understand.) I've had two problems worth watching out for: 1) Try to avoid running it against NFS. It walks the entire synced area every time you sync. Local disk will be two orders of magnitude faster. 2) Be careful syncing between case-sensitive and case-insensitive filesystems. Unison will start failing out if you ever create two files differing only in case.
Beyond that, I'm looking to start using git to version both my code and my textual data. I'm not intending to use git itself to sync the repositories; I'm going to use it for versioning only, and keep syncing using Unison. The reason is because I'm the only user, and for my own convenience I'd like the working copy to be synced. All I really need out of git is versioning anyway; I already have a workable solution for syncing.
Once a term used to suggest something cheap or inferior, shanzhai now suggests to many a certain Chinese cleverness and ingenuity. Shanzhai culture "is from the grass roots and for the grass roots," says Han Haoyue, a media critic in Beijing, who sees it as a means of self-expression.
I almost feel like whoever at NASA picked the poll options must have been a Firefly fan. Of the four choices, "Serenity" is really the only one that goes well with the existing two names, even to a normal person who's never heard of Firefly.
Don't waste a response on this, but maybe you should look into asking Slashdot to give you a no-flood-control bit. If they don't have one they really should. Anybody who's famous enough to be responding to comments on an article can probably be trusted not to spam the site; and it would be nice if those people could do so without having to worry about getting blocked. (I'm thinking also of NewYorkCountryLawyer here, who probably runs into the same problem.)
For anyone who's too lazy to search for it, the specific issue is on lines 259-274. (That would of course be in the "loop forever on leap day" function.;-)
Before the bile starts pouring in, let's take a moment to thank the FCC for having a suddenoutbreakofcommonsense. That they listened is nothing short of incredible, and we should savor this moment and reward them for it, before we start tearing down the proposal for everything _else_ we each think is wrong with it.:-)
Slashdot Mirror
Yeah, I guess I should be clear. I absolutely believe that most failures in healthcare are systems issues. I would never want a nurse to be prosecuted for making a mistake. I just read this story as "a nurse deliberately bypassed a safety feature, resulting in the death of a patient." You're absolutely right that even then, it could be a training issue, or a workload issue, or a combination of factors. I shouldn't be too quick to judge.
In many cases it comes down to the resourcefulness of the nurse. I have heard of at least one case of a nurse who gave an enteral feeding intravenously. The connections were incompatible. Her solution was to attach the two ends together and keep them in place with surgical tape.
I hope she was fired and prosecuted, but somehow I suspect otherwise.
Take a look at http://www.joindiaspora.com/ .
You should also take a look at http://www.joindiaspora.com/ .
So you oppose patents, then? Or do you like mommy-granted monopolies, and just start crying when the other children try to get your monopoly taken away? :-P
Blame CmdrTaco for that -- the document and the summary both state it's not the real IETF. (It was submitted to the RFC editor for consideration as the April Fools' RFC, but rejected.)
I currently use SPF, and am thinking about dropping it. It causes me a massive pain in my ass every time some dumbass with a misconfigured forwarder doesn't understand SPF or SRS, and tries to blame me for the fact that they can't receive email from me. There just aren't enough large sites sending SPF-enabled mail for misconfigured receiving sites to realize they're doin' it wrong.
You should write up your story in more detail (e.g. how you kept your cool and managed to analogize three more jurors into agreeing with you, without getting kicked off the jury) and post it somewhere. FIJA would certainly publish it for you, and it would be a valuable resource.
What this guy doesn't get is that most so-called 'libertarians' don't really like freedom -- they just hate anything that looks like cooperation or collectivism. It doesn't matter whether it's voluntary. So while I applaud his principled stance, he's going to have trouble getting anybody to listen.
See above:
http://science.slashdot.org/comments.pl?sid=1387351&cid=29593149
where someone comments that these people mostly do die of strokes.
You are making a classic mistake: attributing to malice what is explainable by stupidity.
There's a reason why the Pirate Bay is successful and it is rarely mentioned.
ITYM *was* successful. :-\
Unless any of this is documented anywhere that _I_ the consumer can read it, it's all useless bullshit distinctions to me. I just want to know whether my data will work. All your factors are irrelevant to me unless it's documented somewhere what they are, so I can control for them. Otherwise the article's approach of testing randomly is a better and more realistic approximation of the conditions I will actually _get_.
Disclaimer: I have T-Mobile, so all the information in the article is useless to me anyway. :-P
Hmm, according to the docs that's automatically set on OSX. And anyway, I'm not sure what Unison could usefully do besides fail out -- if I have 'A' and 'a' on the Linux end, and they're different files, what should it deposit on the Mac end? Ignoring case does't help make that decision. If it just picked one at random, that'd be worse.
Currently? Just unison -quiet, running from cron. (I have it wrapped in a script that does locking, since Unison doesn't seem to lock against itself reliably, for reasons I don't understand.) I've had two problems worth watching out for:
1) Try to avoid running it against NFS. It walks the entire synced area every time you sync. Local disk will be two orders of magnitude faster.
2) Be careful syncing between case-sensitive and case-insensitive filesystems. Unison will start failing out if you ever create two files differing only in case.
Beyond that, I'm looking to start using git to version both my code and my textual data. I'm not intending to use git itself to sync the repositories; I'm going to use it for versioning only, and keep syncing using Unison. The reason is because I'm the only user, and for my own convenience I'd like the working copy to be synced. All I really need out of git is versioning anyway; I already have a workable solution for syncing.
From the summary (you didn't even have to RTA): "mechanical exoskeleton"
If you own something then you can sell it.
This right here, ladies and gentlemen. This is the cancer that's killing /b/^H^H^H America.
Once a term used to suggest something cheap or inferior, shanzhai now suggests to many a certain Chinese cleverness and ingenuity. Shanzhai culture "is from the grass roots and for the grass roots," says Han Haoyue, a media critic in Beijing, who sees it as a means of self-expression.
Sounds to me like "hack" or "hacker".
I almost feel like whoever at NASA picked the poll options must have been a Firefly fan. Of the four choices, "Serenity" is really the only one that goes well with the existing two names, even to a normal person who's never heard of Firefly.
Don't waste a response on this, but maybe you should look into asking Slashdot to give you a no-flood-control bit. If they don't have one they really should. Anybody who's famous enough to be responding to comments on an article can probably be trusted not to spam the site; and it would be nice if those people could do so without having to worry about getting blocked. (I'm thinking also of NewYorkCountryLawyer here, who probably runs into the same problem.)
Seriously, nothing to see here. This is truly an embarrassment to Slashdot (if that's even possible). Just move along.
Wow. Has "KDE doesn't need users" been a Slashdot story yet? I know it's out of date, but really, that deserves some exposure...
For anyone who's too lazy to search for it, the specific issue is on lines 259-274. (That would of course be in the "loop forever on leap day" function. ;-)
Before the bile starts pouring in, let's take a moment to thank the FCC for having a suddenoutbreakofcommonsense. That they listened is nothing short of incredible, and we should savor this moment and reward them for it, before we start tearing down the proposal for everything _else_ we each think is wrong with it. :-)
Replying to cancel accidental moderation. :-\