Technically, they arent even a business. One is a business when the revenue model works. People in IT tend to forget that.

We have a statistics problem. Thing is, the way successful surgeries vs botched procedures are measured isn't transparent; as an example, my mother died 2 years ago victim to a routine procedure; It was a combination of both "bad luck" (something went wrong with the procedure) with laxity (prolonged weekend, nobody cared about complaints). Because she didn't died on the table, instead from "complications in recovery" (fyi they accidentally perfurated the intestine during the procedure), its "natural causes".

Many years ago, my dad died from meningitis, 8-10 months after a surgery and a very long recovery. I'd bet a couple of fingers it was a hospital-contracted infection during either the surgery or the recovery. Again, a routine surgery took 8h instead of the expected 2.5-3h. Shit happens, we know - surgery is extremely dangerous, and there is a shit ton of stuff that can go wrong.

Thing is, none of this get into the statistics; There are no reliable survival metrics; The papers you sign are riddled with medical terms to isolate you from the consequences (would you do a non-critical surgery if you could end up shitting on a stomach bag for the rest of your life?), and many many doctors are quite happy into "selling you" their trade option. To be clear, the number any doctor presents you is *wrong*; it has no connection with reality; failure rates measure deaths on the table (the best kind of death, btw), and studies extrapolate from badly measured (per-hospital metrics) or non-existing data.

Tl,DR: avoid surgery if you can; If you really need it (after asking for at least 2 more opinions), your health (and often life choices) matter - bad kidneys, weak liver, etc may be the difference between someone rushing it up or giving an extra 20 min to ensure everything is kosher.

I can change the behaviour of many/most applications by just having read/write access to files; Can you give me examples of mainstream applications that are resistant to filesystem tampering when eg.you have install access? Maybe I'm missing something.

You are conflating "not understanding how to build software" with "not knowing how to write code". Most developers I've crossed paths with couldn't build a consistent library, let alone a complete, well written, architecturally sound and useful application. Sure, I also know plenty that don't fall into that category but those are the few.

Problems with deploy? Ask claude, use ssh with key-based auth and he will take care of it :) just saying.

I've been writing code "almost daily" for the last 35 years; been doing it professionally for at least 29 years. I've been around, and my peers consider me a proficient developer. I've built stuff ranging from embedded/os level development to DSL languages, from 3D programming to VBA macros. I wrote software used by me, and wrote software used by millions. In some cases, I've maintained products written by me nore than a decade. By your definition, I must be wrong, truth is I can afford to be wrong - my job is not writing code, is designing solutions. Writing code is often the easiest part, and we're mostly automating it. Thank god.