towerful

joined 2 years ago
[–] towerful@programming.dev 7 points 1 day ago (1 children)

Never mind the damage it did to the launch pad.
And there is concern about possible damage to the other rocket in the FAB

[–] towerful@programming.dev 2 points 3 days ago

I mean, we have rain all the time. I think all forests here are rainforests

[–] towerful@programming.dev 7 points 3 days ago

Someone should peel him like an onion. A tasty tasty onion.

[–] towerful@programming.dev 20 points 3 days ago (1 children)

I'm ok with that. We had special treatment. People didn't want it

[–] towerful@programming.dev 14 points 3 days ago (1 children)

Certainly a juicy onion to take a bit of, regardless

[–] towerful@programming.dev 8 points 3 days ago (1 children)

The fix is clearly to have a group of non-medical people in charge of that pooled pot of money who can deny payments for arbitrary reasons.
I think this is the most sane solution

[–] towerful@programming.dev 5 points 5 days ago (1 children)

Yeh, same. Which is why I said ideally there would be 100% overlap with shifts. Always 2 doctors, offset by half a shift.
Like, that is the fix. Peer review of decisions, easy conference/council/whatever-the-word-is, context can be handed over better (outgoings doc/nurse briefs incoming doc/nurse while remaining doc/nurse listens & supplements)

But I have also been on gigs (I work in events) where there is a rig crew, a show crew and a derig crew.
When everything is meticulously planned out and everything goes according to plan with all the communications in advance, it works. It does. (As a tech, I'd rather set up the kit I'm using). If I know it has been set up according to pre-communicated spec then I can work it. If it deviates and I have been in the loop, I can work with it. But if it turn up and it doesn't make immediate sense then it is many times harder. If I am rigging kit without a clear concrete plan, then I am guessing what the tech wants.
And I also know 2 lampies can't co-light a gig unless they take turns.
Someone has to be incharge, someone has to take responsibility.

But I don't think (and from what I have read, and I'm sure I have been somewhat misinformed) that applies directly to healthcare. Meticulous plans don't exist. Every patient is different. Something minor reported and expected to go away on the last visit of the leaving doc that is then reported as slightly-more on the new docs visit... That could be significant. And a few extra hours on a shift could save a life, because of that easily dismissed/forgotten context/knowledge during a handover.

2 doctors at all times is the fix. Or, actually, a voice-to-text and an LLM.... Likely a decent usage of an LLM.
It doesn't need to know who/what the patient is. It doesn't need to know co-morbidities, existing conditions, medications, treatmens etc. Just that the doctor is interacting with patient A, and here is a summary.
Patent A is the same patient that a nurse interacts with.
Helps with hangovers and context.
Patient A is still in the hospital? Patient A still has a transcribed record that can be quickly summarised by a local (or onsite) LLM.
Using onsite LLMs is no different than using a database. And it doesn't have to be massive. 30m before a shift change, there can be a "notes after this time will not be summarised during handover so previous context can be summarised". So doctors only have to remember the last 30m during a handover, and the rest of the context (even transcripts) are provided to prompt their memory for a better handover. It's an information tool for doctors, not a crutch.
And now I sound like an AI shill.

Sorry for the wall of text. I've been drinking. I hate the "just use LLMs bro", but think they have genuine utility when applied safely and locally.
And I want doctors and nurses and janitors/cleaners/sterilisers/techs of hospitals to be treated like the fucking heros they are.

[–] towerful@programming.dev 43 points 5 days ago (8 children)

We aren't. But it's generally better for patient care. It's the same nurse/doctor seeing through more of the care of a patient with less handovers.
Handovers are where minor details or context can be forgotten, dropped or misunderstood - especially after a really tough shift.
Patients also get to see the same faces more often, which makes them feel like they are being taken care of - as opposed to a part being made in a machine.

But it's wrong. It would be better to have 8 hour shifts with 2-4 hour overlaps between shifts. So it's not a handover, it's an actual rounds, it's actually servicing patients and so on.
But that is likely very intrusive for patients, and 4-8 hours of the shift is with someone else (who you might not like or agree with) and communicating (which can be tiring).

So yeh, it's not great. Understaffing doesn't help, especially since these are people that genuinely care about their work. It's pure exploitation, because it is cheaper and hospital administration can justify it and get away with it (or whatever is higher that hospital admin in the case of free healthcare).

In some cases, it's budget and exploitation. And it's bullshit.
But there is a genuine argument that a doctor who is fully informed and tired is better than a doctor who is fresh and oblivious.

[–] towerful@programming.dev 3 points 5 days ago

As soon as I saw the title, I knew it was going to be "at the start of the transaction".
Nice breakdown of it causing a bug, and how that bug slipped through layers of testing.

[–] towerful@programming.dev 4 points 6 days ago (1 children)

Ah, I must've skimmed that part. Silly me.
Glad my deduction was correct.

[–] towerful@programming.dev 18 points 6 days ago (6 children)

Maybe.
But it is part of CAA regulations: https://www.caa.co.uk/commercial-industry/airlines/dangerous-goods/changes-to-rules-on-the-carriage-of-lithium-cellsbatteries-and-power-banks/

Must be in carry-on and cannot be used in flight.
So, technically the plane was flying illegally.
Fires on planes are NO joke. And lithium batteries love fire, whether starting it themselves or getting hot enough to set other things on fire.

How they discovered it was charging in the hold during flight, I have no idea.
It had to have been a passenger mentioning it.
The cargo hold is completely sealed off from in-flight accessible areas (some older planes have small access hatches that require tools to open).

[–] towerful@programming.dev 2 points 6 days ago (1 children)

I'll grant it should be "a self fullfilling prophecy".
But it never has a "z" in it.
That comes from incorrectly thinking it needs similar similar patterns to other verbs.
And this isn't some "simplified English" Vs "English" scenario. It's not even recognised as part of American English.

https://www.askdifference.com/prophesized-vs-prophesied/

 

(not sure where to post this...)

I had an idea there might be a TUI lib for typescript. A duckduckgo search came up with an article that described exactly what I wanted!
So of course I immediately searched for this fabled tui lib. A quick search didn't reveal anything, and npm can't seem to find it either! https://www.npmjs.com/search?q=Tui
Navigating directly to the npm package page reveals a 10 year old got repo with no actual code... (https://github.com/basarat/tui)

What the scuff is this world coming to?!
This seems to absolutely align with my experience of using LLMs

(Also accepting suggestions for typescript TUI libs that actually exist!)

 

I've been here a while, and I appreciate the community and the defed/hiding list.
I also know programming.dev contributes to upstream Lemmy repos.

I saw another post about another instances funding.
Which reminded me....

Is programming.dev on track for funding?
Need some more donations?
Is there a runway?

view more: next ›