My Stuff
Love
Respect
Admiration
- Leo Brodie
- Avi Bryant
- Alan Cooper
- Steve Dekorte
- Stephane Ducasse
- Doug Engelbart
- Eric Evans
- Brian Foote
- Martin Fowler
- Paul Graham
- Dan Ingalls
- Alan Kay
- John McCarthy
- Steve McConnell
- Peter Norvig
- Niall Ross
- Randall Smith
- Gerald Jay Sussman
- David Ungar
- Rebecca Wirfs-Brock
- ...And So Many More...
My Amps
Links
Archives
- 05/01/2003 - 05/31/2003
- 06/01/2003 - 06/30/2003
- 07/01/2003 - 07/31/2003
- 08/01/2003 - 08/31/2003
- 09/01/2003 - 09/30/2003
- 10/01/2003 - 10/31/2003
- 11/01/2003 - 11/30/2003
- 12/01/2003 - 12/31/2003
- 01/01/2004 - 01/31/2004
- 02/01/2004 - 02/29/2004
- 03/01/2004 - 03/31/2004
- 04/01/2004 - 04/30/2004
- 05/01/2004 - 05/31/2004
- 06/01/2004 - 06/30/2004
- 07/01/2004 - 07/31/2004
- 08/01/2004 - 08/31/2004
- 09/01/2004 - 09/30/2004
- 10/01/2004 - 10/31/2004
- 11/01/2004 - 11/30/2004
- 12/01/2004 - 12/31/2004
- 01/01/2005 - 01/31/2005
- 02/01/2005 - 02/28/2005
- 03/01/2005 - 03/31/2005
- 04/01/2005 - 04/30/2005
- 05/01/2005 - 05/31/2005
- 06/01/2005 - 06/30/2005
- 07/01/2005 - 07/31/2005
- 08/01/2005 - 08/31/2005
- 09/01/2005 - 09/30/2005
- 10/01/2005 - 10/31/2005
- 11/01/2005 - 11/30/2005
- 12/01/2005 - 12/31/2005
- 01/01/2006 - 01/31/2006
- 02/01/2006 - 02/28/2006
Sunday, November 30, 2003
Am I a Bad Programmer?
I reckon I must be. Bob Martin wrote that Debuggers are a wasteful timesink. I have been doing TDD now for about a month, so I'm no expert nor do I claim to be. I've been trying to do TDD in the programming that I do in my spare time, and I still need and want a good debugger. I use a debugger a lot as an exploratory tool. And while looking at a test sure does help (I would rather have a test than not), I still walk through the code with my debugger when I'm in code that I'm new to. I can't tell you how many programming mishaps I have found this way. Sure, the tests ran, but I found things that weren't quite right. To me, a debugger allows you to see the program as it is alive. Simply looking at code is like looking at something dead and reason how it is when it was alive. I'm not an archealogist, so why guess when I can run the program?
I'm not trying to downplay TDD, but I am amazed that anyone would say that debuggers are bad. I see no problem with being too dependent on them at all. I have found that I am generally using my debugger in new code and when my tests fail. I like TDD because I have a short piece of code that I can execute without running all of the program to find a problem. Thus, it makes debugging a lot shorter and easier. I think the two go hand in hand.
I reckon I must be. Bob Martin wrote that Debuggers are a wasteful timesink. I have been doing TDD now for about a month, so I'm no expert nor do I claim to be. I've been trying to do TDD in the programming that I do in my spare time, and I still need and want a good debugger. I use a debugger a lot as an exploratory tool. And while looking at a test sure does help (I would rather have a test than not), I still walk through the code with my debugger when I'm in code that I'm new to. I can't tell you how many programming mishaps I have found this way. Sure, the tests ran, but I found things that weren't quite right. To me, a debugger allows you to see the program as it is alive. Simply looking at code is like looking at something dead and reason how it is when it was alive. I'm not an archealogist, so why guess when I can run the program?
I'm not trying to downplay TDD, but I am amazed that anyone would say that debuggers are bad. I see no problem with being too dependent on them at all. I have found that I am generally using my debugger in new code and when my tests fail. I like TDD because I have a short piece of code that I can execute without running all of the program to find a problem. Thus, it makes debugging a lot shorter and easier. I think the two go hand in hand.
Comments