Then, when you decide to build tools to help you do your job better, you won't get overwhelmed, because the role of the computer is to remember for you. You don't have to remember all those bugs. The wisdom of it is straightforward and can be summarized in the words of Joel Spolsky,
It's pretty easy to remember the rule for a good bug report. Every good bug report needs exactly three things.
- Steps to reproduce,
- What you expected to see, and
- What you saw instead.
Continuing specifically in regard to the steps one takes to do bug reports, we find a blanket statement from Simon Tatham, that, "More information is almost always better than less." which today I also discovered to be the testimony of a professional. Today, I had trouble at home with iPassConnect -- a service that I had 'supported' at Connexion by Boeing, but never really used first hand. The request for help was filed via a web-based request service. Not only did I get to describe the problem, I could even provide an attachment. But only one. So I zipped all the screen shots I had made. Before the end of day it actually became very important that I be able to use that VPN, so I called tech support, and the tech that opened my ticket looked at my description and attachments and said, "I have never seen a ticket that had all the information in it." I said, "Well, they're training me." By they, I surely meant the very organization on who's phones we were speaking. So for a number of reasons, I can say in all honesty that it has been a good two weeks.
I can't type or spell, but that's a different story.
No comments:
Post a Comment