WTF Bites
-
@Gribnit That sounds like a serious outbreak of heliocentricism. Please see your local health care professional regarding that.
He said it was fine and turned his face back to the sun.
-
He said it was fine and turned his face back to the sun.
What timezone are you in? Because your doctor telling you that it's fine, and then avoiding eye contact and intently staring at the floor is not a good sign, even if that's where the sun is currently.
-
He said it was fine and turned his face back to the sun.
What timezone are you in? Because your doctor telling you that it's fine, and then avoiding eye contact and intently staring at the floor is not a good sign, even if that's where the sun is currently.
Don't worry, we were both staring at the same spot.
-
TL;DW: Two patients were sharing a hospital room in Mannheim, Germany. Very little info about either patient, but one was a 72 year-old woman, and the other was on oxygen. The oxygen equipment was making noise, so the 72 year-old woman switched it off. Medical personnel switched it back on and reprimanded the woman. About an hour later, it was still making noise, so she switched it off again. The other patient had to be resuscitated and is now in intensive care.
The woman was arrested. It's unclear exactly what she was charged with; maybe one of the Germans on here can provide some info. It's also unknown whether the woman acted with malice, or if she was mentally impaired by medication, illness or old age. (Presumably, this would affect the criminal charge, which I would expect would more severe, as much as attempted murder — can you be charged with actual murder if the victim is clinically dead for some time but then resuscitated? — if she acted with malice, versus some lesser charge if she didn't understand what she was doing.) But in any case, why was she left unsupervised after turning off another patient's oxygen?
Also, a story about fixing the siding on his house at 03:00 in a storm. "... like any self-respecting man, I went and got a roll of duct tape ..."
-
@HardwareGeek said in WTF Bites:
can you be charged with actual murder if the victim is clinically dead for some time but then resuscitated?
Not in any jurisdiction I know.
But in any case, why was she left unsupervised after turning off another patient's oxygen?
Clearly they thought telling her not to do that again would solve the problem. They're Germans after all
-
@HardwareGeek personally, I’d have posted it in things that remind you WTDWTF members.
-
According to a comment on the video, she was charged with "versuchter Totschlag". According to Google, this translates to attempted manslaughter.
-
@HardwareGeek said in WTF Bites:
[…[ as much as attempted murder — can you be charged with actual murder if the victim is clinically dead for some time but then resuscitated?
Here, and I suspect German law is similar in that regard, the “attempted” makes no difference to how high sentence you can get. You might get lower sentence if the attempt failed because it was pathetic, but generally it's supposed to be the intent that is punished and judges sure hand out high sentences for attempted murders where the victim survived just because of luck.
-
@HardwareGeek said in WTF Bites:
According to a comment on the video, she was charged with "versuchter Totschlag". According to Google, this translates to attempted manslaughter.
This one showed up here as a sideline in the paper as well, and the charge listed was "poging tot doodslag", which does sound very similar to the charge @HardwareGeek mentions, and I'd also translate it as attempted manslaughter.
It's a bit of a weird concept, but it does show up from time to time. Here in NL, it usually means there was intent to harm (but not kill) someone, and death would likely have resulted if not for some unexpected circumstance.
In this case though it doesn't seem like there was an intent to harm, which typically moves us to "dood door schuld" - I think that is "negligent manslaughter" in the US. Still in an attempted version of course.
-
@PleegWat Yes, basically the difference is that it was explained to her that her course of action would result in harm and likely death to the other patient.
That is what moved it from "negligent bodily harm" (not "negligent manslaughter" since there was no death... yet) to "attempted manslaughter"
If the victim dies and the cause of death is likely to stem from this incident, then it'll be upgraded to "full" manslaughter. Not sure what happens if the victim dies after a judgment from the court.
-
Not sure what happens if the victim dies after a judgment from the court.
An appeal, presumably.
-
@Rhywden Right, momentarily forgot she tried it twice.
-
Basically, this guy alone would probably have needed constant supervision. That's not something the people working in a hospital can achieve - not with the financial constraints we put them under. The nurses on the floor were probably running from one problem to the next.
For the most time, yes, but in severe conditions they can. For a couple days before his death, my dad was having a nurse at his side 24/7 for surveillance and care. Which continued also after they terminated life support. But if you're in a good enough state to be walking around, then you're not ill enough for that kind of care I guess.
-
Status: Of course, there's no way to tell if you got timed out, so spamming the easily-lickable "Sync" button can lock you out indefinitely if you don't intuit this and absorb patience from the rancid-butter shitter.
The scenario being troubleshat is: My device isn't getting policies it's supposed to after several hours waiting on the cloud.
Resolution: I dunno, come back in a day maybe. Don't click buttons, that will make it angry and not talk to you even more than it isn't already.
-
-
Why is
using
statement without assignment even a valid C#, other than being a stupid noob trap?
-
@Applied-Mediocrity For those cases where you need the scoped action, but don't need the thing inside. Like something associated with a lock.
-
PowerShell
: Update help.
: Swedish help not available, but English is.
: Update help, in English.
: English help not available, but English is.
: English help not available, but English is.
-
-
@Tsaukpaetra PowerShell is not case sensitive, so no. Also if looking at the error message it does say {sv-SE} in the first and {en-US} in the second, so it did take the flag.
-
-
@dkf Okay, that makes sense. But it that case it should have prohibited
using
a local (or dog forbid, global) declared outside of its scope. A property or method call should acquire the lock and then it can exit the lock on dispose. As it stands, it's a horrible noob trap.
-
@Applied-Mediocrity said in WTF Bites:
As it stands, it's a horrible noob trap.
Horrible noobs need to be trapped, for the greater good of humanity.
-
@Applied-Mediocrity Due to some poorly-designed APIs, I've needed code like this at times:
SomeDisposableType myResource; if(AcquireResource(out myResource)) { using(myResource) { DoStuff(); } }
-
@dkf In practice you get noob resource leaks instead, I'm afraid.
@Medinoc Okay, so
using
statement that was designed specifically to avoid leaks was designed to accommodate poor designs and possibly leak. Yeah, that makes perfect sense.
-
-
PowerShell is not case sensitive, so no.
But what about locale names?
Apparently not—it correctly capitalized the locale in the error message. Unless the capitalization occurs in the error printing bits and not where the locales are looked up …
-
@BernieTheBernie said in WTF Bites:
SomeDisposableType
And I read
SemiDisposable...
and that is that?I propose the
IIndisposable
interface:class BadJuju: IIndisposable misusing (var a = new BadJuju()) {} /* throws ObjectIndisposedException */
-
@Applied-Mediocrity Might be a similar concept.
ASemiDisposable
isDisposable
when it is, andIndisposable
when it isn't (and then throws anObjectIndisposableException
).
-
We're having a problem with SSDs in HPE servers. So I duckducked a bit and found they're offering just what we need: a site that asks you a few questions about your workloads and servers and offers you a disk that's guaranteed to work and certified by HPE.
It's just, Firefox moans about SSL problems beacuse "unknown issuer", and apparently they thought if "certified by HPE" is good for SSD, it must also be good for SSL:
-
@Applied-Mediocrity For those cases where you need the scoped action, but don't need the thing inside. Like something associated with a lock.
I have tokens like that in Java for thread-bound junk, and there (8) needed to supply a useless method to do something with the useless token reference. Does it dispose, or is it just sugar like
WITH
?
-
@BernieTheBernie said in WTF Bites:
@Applied-Mediocrity Might be a similar concept.
ASemiDisposable
isDisposable
when it is, andIndisposable
when it isn't (and then throws anObjectIndisposableException
).Insufficient. Make
Indisposable
the parent ofIndisposed
andIndispensable
.unless disposing with fire
-
-
I don't get why I see this shit everywhere:
Catch every flavor of exception, including the base Exception, just to log it with a slightly different message. The actual type of the exception is included regardless.
Half the time there's copypasta errors where it says the wrong message for the exception type.
-
I'm beginning to suspect our former senior developer Wasn't That Good.
-
I'm beginning to suspect our former senior developer Wasn't That Good.
As a senior developer, can confirm, I'm barely competent.
-
I'm barely competent.
I don't know why omnipresent incompetence continues to surprise me, but I guess I owe my career to it.
-
I'm barely competent.
I don't know why omnipresent incompetence continues to surprise me, but I guess I owe my career to it.
Yeah. Barely competent has served me well. It requires constant attention to maintain, of course. The legendary 10X developers are also, barely competent.
Awhile ago, I was pretty good, and that did not work at all. But then I got better.
-
Same file, keeps on giving.
The constant DBSOURCE no longer exists (nor is there any db connection left to speak of) but its comment lives on!
And there's no apparent reason why scheduler ID is a hashcode of the class name (especially because it's toString'd everywhere so it could have just been a string, which might have been useful).
This part amuses me:
No idea why
createProductsTagsStatus
exists or isn't an enum, but I think it's probably a mistake that it can be "TagsCreatedNotCreated". Not that it affects anything because AFAICT it's a write-only field.
-
there's no apparent reason why scheduler ID is a hashcode of the class name
Any inlinable (and sufficiently lossless) transform of an ID can be used to increase code size while retaining the correlation properties of the ID against other such transforms.
-
-
I don't get why I see this shit everywhere:
Catch every flavor of exception, including the base Exception, just to log it with a slightly different message. The actual type of the exception is included regardless.
Half the time there's copypasta errors where it says the wrong message for the exception type.
Hey, can you access the infamous
PRT
class I mentioned in The Lounge?
-
@BernieTheBernie said in WTF Bites:
SomeDisposableType
And I read
SemiDisposable...
and that is that?"Recyclable" plastics and stuff that might, theoretically, be recyclable, but it's not economically practical, so they'll actually end up in the landfill even if you put them in the recycling waste stream.
-
@error the code formatting seems to go absolutely wild with the clown colors everywhere and the linter seems to think basically all of your code is wrong, according to the underline squiggles.
But what does it mean thatJSONException
is strike-through?
-
But what does it mean that JSONException is strike-through?
Probably
deprecated
.
-
But what does it mean that JSONException is strike-through?
I would guess it's derived from another exception type that is already being caught before it.
-
basically all of your code is wrong
What else would you expect from someone called @error?
-
@Applied-Mediocrity said in WTF Bites:
I propose the IIndisposable interface:
I propose the
IIIIIAmStillEmperor
interface.
-
The constant DBSOURCE no longer exists (nor is there any db connection left to speak of) but its comment lives on!
/** Function f(). * * Functions have to have documentation comments, so here is some. * We like comments here! * In fact we love them so much here you have some more. */
-
@Applied-Mediocrity said in WTF Bites:
I propose the IIndisposable interface:
I propose the
IIIIIAmStillEmperor
interface.Pretty sure someone somewhere has a crash-handler
IGiveUp
interface.