User Experience (UX), WiFI, Xubuntu, Error Messages, Telegram, Wire, Python, PRINCE2, Health
Post date: Jul 23, 2016 9:06:30 AM
Linux User Experience. It took quite a while for me to figure out why WiFi / WLAN wasn't working. Reason? Access Point (AP) was configure to use n standard. But the old device only supported g standard. Guess what, Xubuntu, doesn't indicate any kind of reason for this fail. Just just tries to connect for a long time, and then fails. Yet another example of engineering, how to totally fail and even fail to give any kind of feedback or reasonable error message. After wondering for a while, I enabled gn mixed mode, and tada, everything started to work. Yet, the network list nicely shows the n network and prompts for password, even if the device naturally can't join the network. - Thank you once again for great engineering guys. - Phew.
Based on previous statement, I've always deeply liked applications which provide excellent feedback. Maybe I'll make my next program bullet proof? What? Really? Yes. It starts with try: statement, then all the meaningful code basically 'main()' and then there's code like: except: print(random.choice(['Fail', 'Error', 'Fatal error', 'Epic fail', ' Something went wrong', 'Problem', 'U mad', 'Try again', 'Please fix it', 'Invalid user', 'Tough luck', 'You suck', 'Guru Meditation', 'Suddenly the Dungeon collapses'])). No help text, no any further explanation. If something is wrong, it's the stupid user's fault. Because he/she's not using the program correctly. Please fix the fail (whatever it is), and try again (later). - Thank you. Ok ok, this is pretty much in BOFH category, but some program are just like this. Actually not catching the exceptions would provide default stack trace and give even some feedback and possibly meaningful exception information. But doing it like this, just makes solving the problem much more fun for the end users. Technically the application never crashes, it's totally well managed exit. Making it robust and awesome application.
I'm wondering if the 'Telegram Secret Chat Canceled' is a bug, feature, design flaw or something else? Does anybody know. It's just so annoying that the secret chats get canceled more or less randomly. It's because of chat's getting "out of sync". But that shouldn't happen. What's the root cause of the problem? Is there some kind of security consideration which is source of the 'problem', so it's by design like that. Or is it some kind of fail. Anyway, it's guaranteed to deliver bad user experience (UX). But that's nothing new. It seems that this issue has persisted for several years. I think it's triggered by the immediate key renegotiation failing due to timeout or something like that. But what are the related parameters and so on.
Checked out Dependency injection. There are tons of frameworks which implement this for Python.
Tried Wire, immediately found out that the app delivers poor user experience (UX). Phone number entry sucked totally. Place holder stuck in place, country code separation very unclear. Confirmation entry sucked, link didn't work, required manual re-entry. Great, awesome start. Got issues with audio calls, even on 300 Mbit/s 5 GHz WiFi / WLAN and 1 Gbit/s Internet connection. If something is a fail, that is. Well. Gotta test it with friends too. But first impression wasn't that great. There's still many things to fix. Their web client is also broken, lulz. Great error message once again: "Problems with the connection. Please try again.". That doesn't mean anything at all, it's just as useful as the ridiculous error messages I've wrote about a few bullet points earlier.
Read a book about healthy living, it contained a ton of information. Yes, all the common topics we all see in TV documentaries, doctor shows, and on ever healthy living website. Nothing new. But it's good to remind yourself about stuff like that every now and then. Less calories, more nutrients, daily schedule and so on.
Read requirements for PRINCE2 certification and related documentation.