Firstly, the transaction failed and notified you about the error - that's certainly intentional.

Second, there's failures that would be invisible to you as the customer, such as "instead moving $100 from account A to account B it credited account B but didn't debit account A, without generating an error". Those are mostly the systems I'm talking about being insulated from AI development. Without more detail about the exact problem you had it's hard to tell if it's a failure in customer facing systems or backend infra.

Third, I'm assuming you were able to reach out to the bank directly and resolve the issue by talking to a person (if the issue was really outside the norm), which isn't something you can assume will be possible with a lot of customer service ops these days (or you're going to be waiting hours/days for that callback).

Fourth, you can't really know the error rate of the bank's systems, or how common a given particular error is. It may be a known issue, or it may be a completely unreported one. Assuming it's an error with something on the backend/backbone of the bank's operations, it's running code that can be inspected, reviewed, understood, and fixed - sometimes by a very expensive COBOL consultant.

There's definitely still AI/LLM integration happening, but is kept out of specific areas of the business.

I've seen people bounce off of it, no shame if that happens - in typical JRPG fashion of the time it came out it's involved (there's some non-intuitive progression steps) and takes about 20-30 hours to complete.

There's a DS version which I can't speak to since I've only played the original SNES version, but I understand it adds some additional content that's not required for the story.

I'm a fan of a slightly different version of this that I heard years ago:

"Just because something isn't working as advertised, doesn't mean it's not working as intended."

First, from a technical standpoint the required context window would be massive if you're looking at a person's career/life holistically. Probably solvable, but definitely something to be aware of.

Second, privacy goes completely out the window since you're sharing everything. You don't know what's relevant and what's not up front so you need to provide everything.

Third, you would need a training dataset of all those input variables and their outcomes to be able to provide any sort of useful output. The first set of people to share everything wouldn't be able to derive any value from the tool, and I think you'd be hard pressed to convince enough people to do it to get a useful dataset.

Ever gone down the auto-suggestion rabbit hole on YouTube Kids? You start getting into weird and potentially disturbing territory much more quickly than you'd expect.

The Bar exam in the US didn't start until the 1780's, so lawyers before then weren't "real" professionals either?

It's a ridiculous argument.

A better one might be that the externalities and opportunities for software engineering to kill people, or be directly tied to deaths or negative outcomes, didn't exist or weren't well enough documented until recently. As an immature field/industry that's not surprising, but it does point to a responsibility by the community to push for standards that don't currently exist.

This isn't because you're a "real" engineer, it's because of regulation and industry licensing around specific engineering disciplines that didn't exist until the start of the 20th century. Railroad engineers in the 1800's didn't have the same set of regulations to follow, or the same liability for mistakes.

Software engineering could have similar regulation and licensing set up, though I think you'd find it to be an impossible uphill battle in today's world against the lobbying power of the big tech companies.

Regulation can also break things if done incorrectly/poorly/inefficiently/corruptly.

The question I have about this is whether you would need to get inspections and permitting done if you ever tried to sell the house?

If that's the case the loophole only works for the owner/builder and the next person to own it is going to have to scrape it clean and rebuild entirely. If you ever wanted or needed to sell it sounds like this would complicate that process by quite a bit either way.

I occasionally have to right click a game and enable the compatibility in the settings - that's just a single checkbox. Steam handles the management of pulling whatever the most recent version of Proton-GE is for me and everything pretty much works. There's a setting in Steam itself that you can set a default compatibility tool.

The only games that do shaders preload are Marvel Rivals and Monster Hunter World/Wilds, and even those are quick and can be canceled if I cared to. Even modding is fairly straightforward using something like r2Modman for Steam games or Prism Launcher for Minecraft.

If that's too hard for some people then I bet they also don't run adblockers, which means I've written them off as actually knowing how to use a computer at the most basic level.

All that means that if you're using IPv6 then you're proactively enabling it on whatever is handling your perimeter, which means you hopefully know what you're doing along with all the gotchas that come with that setup.