welch.com/cgi-bin/mt/mt-comments.cgi?__mode=red&id=4507">Timothy Roscoe Carter at May 8, 2003 02:13 PM

If I'm writing software for a small org, I test it, then send it off to the client for further testing. They might pass it on to other testers. Feedback comes back, I make changes, repeat. When released, if it has more bugs, they're fixed in future versions. If it has too many bugs, people vote with their wallets.

For larger companies, the process is more formalized. For some companies, it's very formalized. Most larger software companies have a Quality Assurance dep't filled with testers. The above process applies.

OpenSource projects are somewhat similar to blogs. Search for bugzilla.

Sun's java has its own bugs database (search for it). When I see a java bug, I can go to their database and enter it. Then, Sun will check it out, and update its status: not a bug, will be fixed when, etc. Other people can look through the database to see whether a problem in their software is due to a bug.

Posted by: Lonewacko at May 8, 2003 06:11 PM

Coompared to toilet training, NO!

Posted by: Brooks at May 8, 2003 07:17 PM

I'd say the folks who manufacture Tylenol worked more quickly and efficiently to right a wrong than did Raines and the NYTimes. But if Jayson worked for the LAtimes, he'd just get a column, not the boot. Maybe he'll get Sandy Banks' old job.

Posted by: KC at May 8, 2003 09:57 PM

"Frankly, no newspaper in the world is set up to monitor for cheats and fabricators."

Unless the newspaper thinks those cheats and fabricators are at a golf course in South Carolina. OOOOOH!!

Posted by: Jim Treacher at May 9, 2003 12:44 AM

Or is it Georgia? Wherever.

Posted by: Jim Treacher at May 9, 2003 10:21 AM
Post a comment


Remember personal info?

= true; } else { document.comments_form.bakecookie[1].checked = true; } //--> /body> ent.comments_form.bakecookie[1].checked = true; } //--> /body>