Design Con 2015
Breaking News
Comments
Newest First | Oldest First | Threaded View
rajabavani
User Rank
Rookie
re: Debugging: what questions engineers should ask
rajabavani   9/22/2010 8:24:17 AM
NO RATINGS
Dave, Thanks for the comments. I had a look at your poster and it is quiet simple and practical. Thanks for sharing. Debugging continues to consume significant efforts (and hence cost) among all Software Engineering activities. Following such rules and asking critical questions will benefit engineers who spend long hours in debugging. Regards, Raja Bavani http://www.mindtree.com/blogs/category/software-product-engineering

dagans
User Rank
Rookie
re: Debugging: what questions engineers should ask
dagans   9/13/2010 8:35:19 PM
NO RATINGS
I devoted a whole book, appropriately titled "Debugging" to the subject. It too is a lighter attempt to enable better debugging. But it does work -- all of the general guidelines I've seen are still covered by the 9 rules and their corollaries. So for example, Larry M.'s comment is covered well by rule 3, Quit Thinking and Look. The 9 rules are available on a poster from www.debuggingrules.com. -- Dave Agans

rajabavani
User Rank
Rookie
re: Debugging: what questions engineers should ask
rajabavani   7/20/2010 3:37:36 AM
NO RATINGS
Larry, Thanks for reading my blog. I liked your quote very much. The ability to see or visualize the right thing is very critical to debugging. Regards, Raja Bavani My Product Engineering Blog: http://www.mindtree.com/blogs/category/software-product-engineering

LarryM99
User Rank
CEO
re: Debugging: what questions engineers should ask
LarryM99   7/6/2010 5:40:14 PM
NO RATINGS
I once wrote an article on debugging that included an observation on how a good debugger operates. If I may be allowed to (probably mis)quote myself: "A good debugger sees what is, not what he expects it to be, what he thinks it must be, or what he wants it to be". Literally the developer is their own worst enemy when debugging a system. They know what it is supposed to do, so they come in with expectations that this is what it must be doing. This is why a different person sees bugs that a developer will miss. Larry M.



Most Recent Comments
SpaceBug
 
_hm
 
_hm
 
David Ashton
 
R_Colin_Johnson
 
rick merritt
 
pguptaca
 
MeasurementBlues
 
MeasurementBlues
Most Recent Messages
11/26/2014
7:38:46 PM
Flash Poll
Top Comments of the Week
Like Us on Facebook
EE Times on Twitter
EE Times Twitter Feed

Datasheets.com Parts Search

185 million searchable parts
(please enter a part number or hit search to begin)
EE Life
Frankenstein's Fix, Teardowns, Sideshows, Design Contests, Reader Content & More
Max Maxfield

Book Review: Deadly Odds by Allen Wyler
Max Maxfield
8 comments
Generally speaking, when it comes to settling down with a good book, I tend to gravitate towards science fiction and science fantasy. Having said this, I do spend a lot of time reading ...

Martin Rowe

No 2014 Punkin Chunkin, What Will You Do?
Martin Rowe
Post a comment
American Thanksgiving is next week, and while some people watch (American) football all day, the real competition on TV has become Punkin Chunkin. But there will be no Punkin Chunkin on TV ...

Rich Quinnell

Making the Grade in Industrial Design
Rich Quinnell
13 comments
As every developer knows, there are the paper specifications for a product design, and then there are the real requirements. The paper specs are dry, bland, and rigidly numeric, making ...

Martin Rowe

Book Review: Controlling Radiated Emissions by Design
Martin Rowe
1 Comment
Controlling Radiated Emissions by Design, Third Edition, by Michel Mardiguian. Contributions by Donald L. Sweeney and Roger Swanberg. List price: $89.99 (e-book), $119 (hardcover).