The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Paraphrasing from a Microsoft UX document I read about 'Metro' and task dialogs:
Microsoft wrote something like this:
Message boxes are replaced by task dialogs, which are supposed to be a uniform and fairly large size. One of the criticisms of the standard message box was that it was too small, and tended to get lost against a background of multiple application windows. The intent is that the larger and constant size of the task dialog acts as a cue that you need to make a decision or perform an action when the dialog appears.
FWIW, I hate flat monochrome UI's too. I don't mind the flatness as much, as people were getting out of hand with overly-wide drop shadows on everything and 3D-reach-out-and-grab-your-crotch icons on stuff. I despise monochrome UI's. I'm thoroughly middle-aged, and my visual acuity is pretty poor. It's rough for me to recognize icons that differ only by a few pixels. I also have a hard time figuring out the too-subtle figures of the icons themselves, as they assume a visual language acquired during a childhood filled with video games and the world wide web. Those of us who experienced these developments as adults don't have the same fluency (you lose a lot of language-learning skills as you exit childhood). Part of the problem is that the principal development teams are run and populated by 20-somethings and 30-somethings. No one performs usability testing based on age, since the attitude is they wish the dinosaurs would just f***ing die off anyway.
Instead of a floppy disk, I once wrote an app that used the standard Windows hard drive icon, overlaid with an arrow pointing down to the drive to represent Save...and another icon with an arrow pointing up instead, away from the drive, for Load.
And so my graphics designer career came to an end. It seemed like a good idea at the time.
I always think something, but actually it was a little embarrassing to say it until recently, because it sounds like a bad joke of teens or their dream.
Therefore - in advance and to my defense - is to mention that my SF-Con is a very long time ago, and I (hopefully) with my 40+ already arrived in life.
Especially after the appearance of Windows 10 and its UI appearance, I increasingly recognize a special trend and change with a certain similarity of the UI to the good old ST TNG.
Looking back at the past 20 years and the current direction, first the good old fold-out phone, then iPhones, pads, and other mobile devices. In addition, then a little loose connection with Linux, and the growing storm clouds, whereby a certain weakening of the desktops in the direction of mainframes is tried.
So also in now relatively flat and now universally expectant UI, which should now get more and more tabs.
Maybe someday our dear windows will disappear completely.
Something about which we often break our head:
"In the name of the Compiler, the Stack, and the Bug-Free Code. Amen."
Yeah, when was the last time you saw a 20 year old web-developer worrying about anything else, other than what flavor of fashionable tech they're using? Who cares if you have a 5% contrast between the grey background and the grey text? Who care about 25 MB for the landing page. Who cares about the fact that a core-i7 at 5 GHz still can't run your page responsively, let alone fluidly.
Native development is only a tiny bit less worse, because they can't just import a magic 300 MB library to show a button.
PS: I add and test accessibility features to all the apps I make, even though I never use them. Why? Because I make apps for users, not for store ratings.
My biggest peeve with latest designs is the missing Apply/OK buttons in windows 10. Once you change something there used to be an OK button that gives you an immediate confirmation that what you have done is actually applied. These days you make some changes and there is no buttons to confirm and it makes me confuse did it work or not and then most of the time I go back to same screen just to be sure.
Some designer ( Self proclaimed artist ! ) is getting paid a million bucks somewhere to come up with such a stupid design.
Zen and the art of software maintenance : rm -rf *
Maths is like love : a simple idea but it can get complicated.
That's actually very easy. Under the new paradigm, there's no such thing as "apply". Apps aren't databases with commits, if you change a font size or enable a background service, everything should be completely dealt in the background. Think of the WiFi on/off button in your smartphone. You don't change the wifi to off and then press apply: you turn it off and wait for the darn thing to actually turn off, which is relayed by the button changing color, indicating status.
A fine band, very popular here in Chicago. They had a unique almost midwestern sound that appealed to me. 'Behind the Wall of Sleep' a great song, sadly applies today.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle