Page 8 - MSDN Magazine, October 2017

Editor’s NotE
There are things that send me into immediate rage. Drivers staring at their smartphones when the light turns green. Or when I snag the wire of my earbuds on an object so they get ripped forcefully out of my ears. Or, almost any time I have to print something.
Not to get all “if we can send a man to the moon,” but how can it still be this frustrating to shoot a few bits across six feet of USB cable and have them laid out properly on a piece of paper?
I was thinking about this after reading David Platt’s Don’t Get Me Started column this month, where he concocts a handy metric to determine the difficulty and brokenness of a user experience, inspired by his struggle to connect an iPhone to the Harvard University Wi-Fi network. His column got me to thinking about another mundane-yet-frustrating computing experience, and one that’s been around for decades: printing.
In an age of smartphones, autonomous cars and AI-driven assis- tant technology, it’s astonishing how little printing has changed since 1995. Printing a document is like lobbing a really unreliable hand grenade over a wall. Your grenade rolls around in the print queue for a few seconds or forever, depending on the whims of the printer driver, the connectivity between printer and PC, ink and toner levels, and a host of other variables. I’ve opened the print queue window after failing to see activity, only to discover a mob of failed and forgotten print jobs stuck in there. It’s infuriating.
I asked Platt about this, and he was blunt. “I cringe when my wife announces she’s gotten a document that she needs printed.”
Platt gets especially worked up over the unhelpful error messages from his printer. “Unable to print because printer is offline,” said Platt, a professor at the Harvard University Extension: “If one of my UX students threw such a cryptic message, I’d flunk his sorry ass so fast he’d change his major to Sanskrit.”
Any IT manager can regale you with stories of undiagnosable printer failures, but even at the home-office level printing is an exercise in fail. When I try to print, my Windows 7 home PC and Windows 10 laptop both often show duplicate printer instances in the Windows Print dialog box. Should I send the job to the printer
MICHAEL DESMOND
Misprint
named Brother HL-2340D series, or to Brother HL-2340D series (Copy 1) or (Copy 2) instead? It’s insane.
It doesn’t have to be this way. The solution to bad user experi- ences is better developer training and education. Big ticket events like Microsoft Build and Ignite are incredibly important in this regard, but I’m a particular fan of smaller conferences like Live! 360, which focuses on hands-on experiences and face-to-face interac- tion with presenters and experts.
Printing a document is like lobbing a really unreliable hand grenade over a wall.
A few weeks ago I hosted a Web cast with Dr. Doris Chen, a senior developer evangelist at Microsoft is presenting a pair of technical sessions at the Visual Studio Live! event in Anaheim later this month (bit.ly/2wZ5fI7). Her work informing the dev com- munity on Web and JavaScript development is vitally important as we continue to build out and rely on Web-based software and services. Looking forward, the Live! 360 event in Orlando (Nov. 12-17) is another opportunity for developers to advance their craft by working in close quarters to some top minds in the industry. You can learn more about the event at bit.ly/Live360FL.
Look, I’m not saying that attending a hands-on technical con- ference will spare anyone the indignity of being flummoxed by the Windows Print Queue. Heck, my Windows 7 desktop spawned a Brother HL-2340D (Copy 3) in the printer list just this afternoon. So, the struggle continues. But it’s events like Visual Studio Live! and Live! 360—small, accessible and hands-on—that can help move us all to a better place.
Visit us at msdn.microsoft.com/magazine. Questions, comments or suggestions for MSDN Magazine? Send them to the editor: mmeditor@microsoft.com.
© 2017 Microsoft Corporation. All rights reserved.
Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, you are not permitted to reproduce, store, or introduce into a retrieval system MSDN Magazine or any part of MSDN Magazine. If you have purchased or have otherwise properly acquired a copy of MSDN Magazine in paper format, you are permitted to physically transfer this paper copy in unmodified form. Otherwise, you are not permitted to transmit copies of MSDN Magazine (or any part of MSDN Magazine) in any form or by any means without the express written permission of Microsoft Corporation.
A listing of Microsoft Corporation trademarks can be found at microsoft.com/library/toolbar/3.0/trademarks/en-us.mspx. Other trademarks or trade names mentioned herein are the property of their respective owners.
MSDN Magazine is published by 1105 Media, Inc. 1105 Media, Inc. is an independent company not affiliated with Microsoft Corporation. Microsoft Corporation is solely responsible for the editorial contents of this magazine. The recommendations and technical guidelines in MSDN Magazine are based on specific environments and configurations. These recommendations or guidelines may not apply to dissimilar configurations. Microsoft Corporation does not make any representation or warranty, express or implied, with respect to any code or other information herein and disclaims any liability whatsoever for any use of such code or other information. MSDN Magazine, MSDN and Microsoft logos are used by 1105 Media, Inc. under license from owner.
4 msdn magazine