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.
Your URL (optional):
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
As someone with over 20 years of software development experience
and currently a small business owner, it has been a pleasure working
with Avonelle. In addition to being a talented developer, Avonelle also
has database expertise and system design skills. Avonelle is open
minded and willing to discuss various methodologies for achieving a
project goal. She is also not afraid to ask questions which is vital in
a software development project. Her up-front project cost (not
estimate) is very helpful in budgeting for a project.
--Dwayne Wolterstorff, Owner @ Fair
Copyright © 2013 Avonelle Lovhaug. All Rights Reserved.
Sitefinity ASP.NET CMS