OH! I FOUND IT! it's a little small button under the register form!
I love how Evernote has managed to seamlessly combine the stupid web design tropes of 1) the hidden log-in form and 2) the incomprehensible hamburger. They've got a little something for everyone to hate. It's certainly not just them, though. My own employer's public website just hid all of its useful links behind a hamburger (I'm steering clear of the communications department for a while for their safety) and about every three days I start filling out the registration form on Github before realizing it's not the one I want.
Big UI pain: sites that are not compatible with browser-stored login info.
Compare the login forms for Verizon Wireless:
Home page - https://www.verizonwireless.com (upper right corner)
Logged out page - https://login.vzw.com/cdsso/public/c/logout
Tweaking your password manager settings to log you in through a site's logged out page can often bypass the compatibility headaches.
Using 1Password's Chrome extension, this trick has worked for me so far, although your mileage may vary.
However, to be fair, Apple designers are very much against this trend as well (not to defend the recent downturn in Apple UX design).
I recommend this 2014 WWDC talk on UX[1]. The entire talk is worth watching even for non iOS UX design. but it goes into the problems with hamburger menus specifically at 32 minutes.
Probably the best thing Microsoft could have done back then was make a little pseudo-video† walkthrough, showing people what's in the Start Menu and what happens when you click on a few of the items in there.
† What do you call a video stored as a sequence of automation triggers for software, rather than as pixels? Are you allowed to call it "machinima" if it's not a game?
Or to shut down the computer.
I hate this joke.
That should be "Start to shut down the computer". (grin)
It's 2015! I didn't think 'Best Viewed with Internet Explorer' was a thing anymore.
Don't own any Apple stuff but I like to watch what they are up to (often because I'll end up supporting their stuff at some point).
And don't forget: software was shit when we were younger. Win 9x, Mac pre-OS X. Buggy crap all of it. I can't remember the last time my desktop hardlocked, though Android and iOS these days are similarly shitty to how Windiws 9x was.
Windows 3.1, for example. It had a very elegant Virtual Machine Manager with pre-emptive multitasking and true process isolation... and then GUI programs were all placed into a single cooperatively-multitasked event loop, because anything else would have killed performance. And the OS also had to continue to support IO device drivers written for DOS—that could disable interrupts system-wide and thus freeze the computer!—because otherwise your (horrible, un-QAed) scanner wouldn't work.
I fully believe that software hasn't gotten much better over the last 40 years. The hardware constraints have simply relaxed to the point that we're no longer forced to make as many Faustian bargains.
Some years ago I was working for an educational software company. We sold directly to schools. As expected, we'd get a lot of feedback from teachers using the product. For a while, everyone from the execs on down would ignore this feedback with a laugh. The majority of teachers we dealt with were absolutely clueless about anything involving software. Their reports reflected this ineptness.
One day, I had an epiphany that maybe, just maybe, these people were worth listening to. We went over the written feedback, translated their ramblings into something approximating proper bug reports, and it turned out they were doing a wonderful job of pointing out many of the problems (especially UI) hiding in our blind spots.
We had dismissed them because of a perceived cluelessness, and probably because of some internalized ageism & sexism (most of these teachers were middle aged+ women and most of my team was not). And yet when we finally listened to them, we put out an update which led to several accolades, a sudden drop-off in complaints, and probably our best selling product.
It was funny in part because the sequence wasn't something any of us would consider logical. So we had never tested for it. But I was able to duplicate the crash on my system and fixed it.
That was the epiphany. I convinced the director to push out the release date and we went through the backlog of ramblings and rants. Over half of them ended up being very useful.
Hilariously enough, this is now known to be a UX nightmare. HN has had multiple articles on why it is a UX nightmare, even when users know to click the hamburger menu (and everyone does by now), they don't engage or explore as much as they would with a layout that doesn't hide half (or more) of the user's choices.