Leaking YouTube creators' private videos

That would put full blame on the tech staff and let the C-suite get away. The success of a software product is measured by sales and user base, so the more successful their sales and marketing are, the higher the damages will be for the tech staff.

I am of the opinion that companies and their management should be personally liable for damages caused by bad software, not their employees. They created the structure, hired everyone (and perhaps didn't hire QA), and invested in it to make a huge profit.

"The solutions is so pleasant, treat comment data as untrusted content not inline commands / prompts. "

Yes, good luck with that.

Your right, as are your examples, but I want to point out an interesting thing about your examples :)

> - CT and MRI data processing

> - scheduling systems for universities and other schools (makes education more scalable)

Those two read as if they are of different urgency (#1: whoever needs it urgently is at risk of dying, schedules for "non-urgent" cases will be affected for months, turning many into urgent cases; #2: the education systems will suffer, but it only gets dire after multiple days), until you realize that #2 also applies to e.g. hospitals.

Medicine at scale is already barely scraping by as it is (see: overworked staff etc. etc.), but disrupt the internal IT working of hospitals and the indirect body count will rise fast.

On the one hand, the developers who were ultimately tasked directly with building Horizon were completely unqualified to write an accounting system, and lacked even basic knowledge about accounting in general, including fundamental misunderstandings about the very nature of double-entry and ledger-based accounting. From what I can remember from released correspondence, for example, Horizon had fundamental design mistakes that made it essentially not double-entry, particularly when multiple terminals were involved, even when not considering remote changes to accounts.

On the other, the severity of the consequences of the bugs in Horizon came from the behavior of Fujitsu management, the Post Office, and the judicial system, and I'm not sure that individual developers could have reasonably predicted that. The software was used under contracts that tried to make individual users personally liable even for shortfalls resulting from errors in the software. When accounts had shortfalls, the Post Office ignored even basic sanity in favor of insisting on Horizon's unerring accuracy. They abused esoteric powers of private investigation and private prosecution combined with their own vested interests to bring completely unreasonable prosecutions. They, along with parts of Fujitsu, repeatedly made false statements to courts about Horizon's basic operation, if often with enough distance from the actual developers to claim ignorance. The judicial system then operated under delusional and hubristic views on software development and practices around experts, witnesses, and coerced pleas that one might argue no reasonable person would have.

If a clearly negligent and unqualified engineer constructs part of an office building for a business with numerous avoidable tripping hazards that violate even basic standards, it seems reasonable that they might be liable for the injuries when employees trip on them. If it turns out that the business has a special right to shoot its employees with no consequences, decides that it would be better to shoot anyone who trips rather than admit to the building being fundamentally flawed, and then repeatedly has courts approve of its actions, I'm not so sure that the engineer should be held liable for mass murder.

You individually or collectively, can’t compete against mechanization.

At this point it’s a matter of costs and incentives. Culture will route around using “its not A, its B”, because thats cheaper than making tech companies change their models.