Hot #UX take: Instead of showing "unexpected #error", apps should expect more errors.

@CyReVolt
It was clearly expected enough for something to show that it happened, instead of the app or OS just crashing.

See also #GitHub: "Something went wrong."
Thanks, um... 🤷

@CyReVolt just show "expected error"

@CyReVolt Did that once.

One of my colleagues frequently mistyped "BYTE" (a directive for an assembler).

So any time an unrecognised directive was found the error message was "[colleague's name] can't spell BYTE".

@CyReVolt that's one of the reasons why I tend to not really like e.g. windows and in general some apps pretending to be user-friendly..

Like, being this non-specific is not user-friendly at all... it's like saying "well there was an error, please figure it out yourself, too lazy to tell you what actually happened" in the name of user-friendliness...

Your call, Deutsche Bahn.

@CyReVolt you are now free to choose any other connection, even those not indicated on your ticke^W internet.

@jer Internet? You think that works here? xD

@CyReVolt how so?

@mimi It's tough, really tough.
A good thing is to regularly walk through all the "TODO: handle error" comments in an existing codebase. Often enough is it a matter of stakeholders caring, unfortunately. I'm essentially asking for stakeholders to please care. 🥺

@CyReVolt ahhh! yes that makes sense :3

Well, ÖBB same vibe!