towerful

Yeh, for 99% of casual internet users... they just aren't going to care about that.
They don't want their email/Facebook/back account pwnd.
Like, at all.

It's like saying that 0.01% of traffic fatalities are because an airbag forces your head into the roof of the car. So you should wear a helmet when driving.

You aren't wrong.
Internet is a massive part of our daily lives. We should be able to fully trust the things we use to interact with it.
But convenience is going to win

That's fair.
What would you have them do? What are they missing?

And directional radio towers ( https://en.wikipedia.org/wiki/AT%26T_Communications_(1984%E2%80%932010)#AT=&T_Long_Lines= ) and satellites. Both of which are wireless.

So yeh, wires have been used in establishing the internet. But wires are not a requirement for internet.

It's like rain can make things wet. But something being wet does not require rain.

Internet is internetwork (ie inter-network), meaning a network of networks.
Wires are not part of the definition

Yeh, fair question.
Recently I built a Non Linear Editor for Vimeo VODs.
The server downloads the VOD, extracts key frames using FFMPEG, allows the user to create a bunch of sections and where they get uploaded to, then FFMPEG does a stream copy to extract those sections, and then upload them.

I knew all of that was possible. I had never done HTML5 video players, I had never spawned FFMPEG from typescript, there was a lot of html/CSS that I didn't have experience with.
Previously, I would have passed on this work.

But after defining a plugin system for source/destination (so it can be used with YouTube or whatever), and splitting each stage into workers, the code itself is fairly easy to evaluate.
I didn't need to know how to get to the result, I just knew what shape the result should look like so I could drive the LLM, and then I just had to read the result and google anything I didn't understand.
And ultimately, I don't really care "if it's good or not". The definition of "good" is that it works and is robust. Other than that, it's looking for code smells.

I guess I am lucky that most of my work is "one and done" instead of long-term support.

Wow, this violates privacy! You mean this scans for nearby devices? Completely exposing nearby consumers of those devices? Totally illegal

\s btw

Sure, or make a good product?
That's what other companies do. They make a good product, and people then depend on it.
The shitty VC companies then enshitify.
The actual "we believe in our product" companies continue making a good product.

As a solo dev, Claude has moved me from a "code writing developer" to a "system making developer".

Someone would come to me with a problem, I'd chew it over come up with a plan and execute it to the best of my ability. And I loved writing the code, solving the problems, learning new stuff, and ultimately seeing something I built get used and make other people's lives/jobs/whatever better.
But many times I would come to the conclusion that it's beyond my skillset (or I could do it, but the sheer quantity of learning would mean I don't hit the deadline or that I wouldn't be confident in the result) and not take on the work - despite understanding the problem they want to solve.

Now, someone comes to me with a problem and I either say "yeh, I can solve that. But let me dig into it a little first", or I say "I don't understand that enough to be able to design a solution for that".
It's no longer beyond my skillset. I have to understand the problem presented, I have to understand what the users want, and I have to understand what the result is. From this, I can know what the code/architecture/frameworks/stack will probably look like.
That's the first step of solving a programming problem.
I don't necessarily have to know/learn exactly how to achieve it.
It feels like I've gone from solo-dev to manager.
Thankfully, I guess, I've done full-stack, k8s, native app development. So I have experience.

Which brings me to my point:

I spent a few minutes reading through the documentation to better understand how the Astro configuration worked.

I've had this exact scenario.
Then I point Claude to the docs, and then it "knows" how to solve the problem.
I point Claude at the docs because I know the specific software can solve a part of my problem, because I have evaluated previously that it can.
I don't necessarily know exactly what I'm looking for, or what exactly the answer is. I don't necessarily know the keywords to be able to find it on DDG.
But Claude could probably suggest something, and I'll know what I'm looking for when I see it.
I've even had Claude build it's own docs from a GitHub repo of docs because the actual API docs are trash (looking at you Vimeo).

LLMs aren't smart. They are expensive to run. And they take a LOT of the fun and knowledge out of programming & development.
But they are a tool.

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

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

"Frank", it I don't think that name is in the same ballpark as you are looking for.

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.