Developer Insights – Stories & Analogies

Gaining Insight into Software Development by looking around

Would you eat here again?

with one comment

Last week, a group of friends were going to get together for lunch.  The restaurant, chosen before I was invited, happens to be one where I saw some insect life on my last visit.  So I declined to join them.  I didn’t bother to provide my reasons nor did I suggest another place.

Now this last visit was about 10 years ago.  You might suggest that there should be a statute of limitations for these sort of things and that I am being totally unreasonable.  I would agree with you.

But then what is the formula for calculating the time?  Does it matter if it was a single critter or multiple?  Are mammals different than insects?  Does the ownership of the restaurant matter?  Does the cuisine matter?  How about the restaurant next door?  How about other establishments in the same chain? Does it matter if it occurred during your first visit to the establishment or if you had been a long time patron?  Does it make a difference if it occurred before you had ordered the food or as you were paying the bill? Would it matter if you were there alone or if you were there on a date?  How about if it occurred on a special and memorable occasion, say Mom’s 50th birthday?  And where were the health inspectors?  Did you report the sighting to the waiter? To the health department?

Given the alternatives, I am willing and able to go elsewhere.


So how does this relate to software development?

  1. How would you feel about discovering a bug in the development tools that you use?  Would it be more worrisome if it was the compiler or if it was the debugger?  How about in the third party libraries that you are using?
  2. Are bugs encountered during installation more worrisome than bugs encountered during an uninstallation process?
  3. Does a defect in one piece of software influence your opinion of the likelihood of a defect in another piece of software with similar functionality, say a defect in one compiler is likely to appear in another compiler?  a piece of software from the same company?
  4. Do you know what software uses the same underlying code?
  5. Do you know what code was written by the same people?
  6. Do you know what code  was written with the same processes?
  7. Do your customers have different reactions to defects?
  8. Do you expect software to have certain “defect density”?  If testing uncovers an abnormally large number of defects, do you congratulate the testing organization?
  9. Do you report defects to other engineers? to other teams? to other organizations? to other companies?
  10. Do you believe customers report all the defects that they encounter in using your software?
Advertisement

Written by amckale

January 24, 2010 at 5:27 am

Posted in Uncategorized

One Response

Subscribe to comments with RSS.

  1. I think the question of cuisine is relevant. I know of folks who, on finding one bug in an MS product will declare it a validation of all the failings of MS, but will pass over one in (say) OpenOffice without a pause.

    As for me, when it comes to restaurants, as long as it isn’t in my food, I don’t mind much.

    I like the idea of being able to screen out all software that Jo Smith ever touched. :-)

    柏大衛

    February 17, 2010 at 5:41 pm


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Connecting to %s

Follow

Get every new post delivered to your Inbox.