Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
I hate interfaces with icon only by default.
Most time you don't understand what the fuck the icons should represent...
Error messages are even worse...
It shouldn't be a big hassle to support an error code, a link and a short descriptive message in a text box...
But yeah.
Most of the time it's: oxooo8a permission error.
Okay.... Tell me more motherfucker :@ -
@IntrusionCM since when is 'o' a number?
-
@electrineer error code, not number.
:)
Hexadecimal is soooooo out of date.
Why not using all characters in the alphabet?
Just for the crazy fun? -
Weirdly enough, I think this is because as developers, we're all insanely turned on by error beep codes coming out of our motherboards or devices when they are broken, and we want to reproduce the insane sexual lust we feel from having to describe the blessed sounds into google to find out what's wrong with our baby.
Though I have to agree that text on screen with some fancy code just doesn't do it for me either. I'm thinking we should start using sound to be retro or maybe flashing lights/icons -
Or atleast put hyperlinks so that user can directly click the text and get the relevant support page. I can't think of a reason why this isn't the norm. On client side, you don't have to do much. Just subclass whatever you were doing before and add 10 lines of code. On server side, you just need a static site generator.
-
Edit- these links don't even need to be hardcoded for each error separately. Links can be something like https://abc.com/support?error={code}.
This is a gripe about modern UX interfaces. UX interfaces need to have better ways to get information displayed in text as text. It is exceedingly annoying to be presented with an error message in a dialog with a cryptic error code. The user is forced to transcribe the error message to try and figure out what is causing the error. Just make the text copy-able with normal cut and paste interfaces. I think this should be a standard in interfaces that present text to make it easy to copy the message or text from interfaces. This makes information sharing easier and less cumbersome to the user. This is definitely a mindset change for UX. This is mostly a gripe about desktop. Phone systems are just shit to begin with.
rant
copy/paste ux