"Debuggers are based on the idea that the code base has enough places bugs could happen that the work of locating the bug is involved enough to justify machine assistance. This is not true of well-tested code. More importantly, the whole point of [T|B]DD is that you identify the bugs before you write the code. As tools which track down bugs in existing code, debuggers presume and encourage a workflow which is exactly backwards."
skip to main
|
skip to sidebar
Software is about people, not code.
About Me
My name is Matt Blodgett, and I believe the most important problems in software development are non-technical.
I write from Chicago, Illinois.
Contact Me
I'd love to hear from you. Send me an email through my contact form.
Blog Archive
-
▼
2007
(
67
)
-
▼
October
(
10
)
- They Got Rob Conery, Too !?!?
- Brain Food 10-26-2007
- Visual Studio Tip: Navigate Backward/Forward
- Easy Notifications with System.Media.SystemSounds
- Debuggers Considered Harmful?
- Web 2.Overload
- What's It Like to Be a Web Developer?
- ASP.NET DropDownList for the 50 States
- ReSharper Tip: Go to File by Name
- Dear Twitter
-
▼
October
(
10
)
2 comments :
You assume a workflow that is in many practical environments theoretical. Are you a student?
I just downloaded some open source code i need to include in my application. It comes with tests. The tests fail. I am happy to have a debugger to go through it.
I'm not advocating getting rid of debuggers (I use them all the time). I just posted that quotation because I thought it was an interesting concept.
And no, I'm not a student.
Post a Comment