"Oops! An unexpected error has occurred."

1. Isn't 'unexpected' implicit in the need to notify the end user of an unspecific error they have no agency to attend to? "Sorry, breaking character here and pulling back the curtain, Something Didn't Go As Planned. Whoops."
2. After the first three screenfulls of such alerts, the error is no longer exactly unexpected by said user, contextually speaking.
3. I need more sleep and/or coffee.

@Momentrabbit I find that most developers write code that assume that everything will have been going to plan up until that point at every point, which means that once one thing has gone wrong, the likelihood of more things going wrong goes up sharply.

Most users intuit this quickly. Most software, sadly, does not.

Sign in to participate in the conversation
Awoo Space

Awoo.space is a Mastodon instance where members can rely on a team of moderators to help resolve conflict, and limits federation with other instances using a specific access list to minimize abuse.

While mature content is allowed here, we strongly believe in being able to choose to engage with content on your own terms, so please make sure to put mature and potentially sensitive content behind the CW feature with enough description that people know what it's about.

Before signing up, please read our community guidelines. While it's a very broad swath of topics it covers, please do your best! We believe that as long as you're putting forth genuine effort to limit harm you might cause – even if you haven't read the document – you'll be okay!