Go Back
Posted by: Avonelle Lovhaug
Publication Date: 3/21/2008 5:00:00 PM
"When I used the software today, I got an error. Can you fix it?"
This is the exact text of the email I received. No specifics on what she was doing when she got the error. No information about the error message itself.
Even worse, this particular user helps other users setup their software. So I can't even try to log-in as her - frankly she could have been using any number of accounts.
If you have ever felt that a software developer wasn't being responsive to a bug you have encountered in the software, stop and think for a moment. Ask yourself these questions:
If you answered No to any of these questions, then I'm not surprised you are frustrated. The developer is probably frustrated too.
If you really want to solve the problem, here are three tips that should help you give that developer enough information to troubleshoot your bug:
Providing specific information about your problem will mean that it will be solved much more quickly. That should make everyone happier.
Category:
Name:
Email (optional):
Your URL (optional):
Comment:
Type the code shown
Top 5 Programmers to Avoid
What everyone should know about bugs
How to tell if an estimate sucks
The Secret to Building a Crappy User Interface
The Problem with Selecting the Lowest Bidder
5 Ways to Control Software Development Costs
Avonelle is a talented expert in her field. She has blended well with our team and built applications that we are proud to deploy to our associates. Her talents helped us execute a vision expediently and with quality. If we could do it all over again, we wouldn’t change a thing.
Peter Edstrom @ Renewal by Andersen
Sitefinity ASP.NET CMS