The other day I had to print out an 800-page file (yow!) and rather than push my decrepit old printer over the edge into madness, I decided to print it at Kinkos. Last I checked, Kinkos had this nifty feature where you could upload a file to their Web site, they’d print it and you could just pick it up. Quick and easy. Well after that process errored out due to the size of the file, I elected to install the new “Print to Kinkos” add-in that allows users to, like the name suggests, “Print to Kinkos” directly from within an application. Cool!
So I started the installation process. And waited. And waited. Then waited some more as the process detoured to install the .NET Framework first (”Hey! You don’t mind if I bring a friend along on the install, do ya?”) Then I restarted my computer. Then the install resumed. Then I waited. And waited. In Kinkos’s defense, nowhere on their Web site did they promise that the install would be “quick.”
As I rearranged my morning schedule accordingly, it dawned on me that the promise of technology is a wonderful thing, but that’s one of the very reasons its occasional failures (or even slowdowns) are so enraging. It made me think back to other instances where technology has inspired me to new heights… of madness:
Bug Bash is a comic strip written and illustrated by Hans Bjordahl. Bug Bash is a comic strip about technology: managing technology, the business of technology. It's about project management and managing projects through the dull world of Rational Rose, use cases, and requirements. Functional requirements, user requirement, functional specifications, design specifications, call it what you want but it's still the bane of project managers. And when you're done with that, you can think about all the fun that comes with timelines, scheduling, estimates (PERT estimation anyone?) and resourcing until Gantt charts are coming out of your ears. Let's not forget the risk management in the software engineering life cycle. Maintaining the project is just as much fun, managing what was initially set out in requirements and trying to keep feature creep / scope creep in check with change management. If any of these words send nightmares to you, the project manager, then this site probably rings true with you. (Who Links Here?)