Jim Starkey wrote:
Something that drizzle might consider is systematic, public bug
analysis. It's a little ego wrenching at first, but a bug by bug
analysis of howa bug occurred, how it didn't get caught, and how it
might have been prevented in the first place is well worth having,
particularly if it needs to more robust engineering practices.
+1. No, +10. :)
To be fair, our bug "lives" are fully public at the moment, with nothing
hidden from view since everything is done on Launchpad. But, that said
I think it's a great idea to:
a) Be as verbose and descriptive on the bug reports as possible about
why or how a bug occurred (especially regression bugs)
b) Openly talk about the causes of the bugs and why it wasn't caught.
c) If a bug exposes an architectural flaw, blog about it and open up the
discussion to see what solutions anyone can see to the problem. Many
hands make light work.
<snip>
Bugs, in most cases, aren't personal failings, but weaknesses in
architecture that require a greater understanding that is humanly
possible. Spending some time thinking about the nature of bugs found
would probably be instructive for all involved.
Absolutely. I don't view bugs (or even architectural failings) as a
personal failure at all, but a learning experience and a chance to
improve the product. I think it makes for a better product when
developers can detach from the "I own this" type of perspective about
code and instead think about the product as a living, breathing,
mistake-making, and ever-improving group effort. That way, personal
feelings don't get in the way of fixing, refactoring, and improving the
project.
To salve the precious egos of those involved, it should be universally
recognized that he or she who writes the most code is likely to
introduce (or expose!) the most bugs.
Yes, good point, and like I said above, there's nothing wrong with bugs.
I'd rather have 1000 known bugs that we're working on fixing than 1000
bugs we don't know about. Bugs are a natural side-effect of coding, and
the greatest coders in the world have bugs in their code. Nothing wrong
with that. What's wrong is hiding bugs or taking them personally.
Cheers,
Jay
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
