Comments on: Smoking craters are good http://docwhat.org/2009/10/smoking-craters-are-good/ Some men are discovered; others are found out Mon, 07 May 2012 09:44:57 -0400 hourly 1 By: docwhat http://docwhat.org/2009/10/smoking-craters-are-good/comment-page-1/#comment-6451 docwhat Mon, 01 Feb 2010 18:38:52 +0000 http://docwhat.org/?p=473#comment-6451 Yes. Good point; it should blow up in such a way that the developer can troubleshoot it. One of the reasons I hate threading. Glad you like IAT. :-) Yes. Good point; it should blow up in such a way that the developer can troubleshoot it. One of the reasons I hate threading.

Glad you like IAT. :-)

]]> By: docwhat http://docwhat.org/2009/10/smoking-craters-are-good/comment-page-1/#comment-6450 docwhat Mon, 01 Feb 2010 18:38:10 +0000 http://docwhat.org/?p=473#comment-6450 Not necessarily "The" developer, but "a" developer. The "is the code maintainable" issue is separate, but just as important. Not necessarily “The” developer, but “a” developer.

The “is the code maintainable” issue is separate, but just as important.

]]> By: Richard Remington http://docwhat.org/2009/10/smoking-craters-are-good/comment-page-1/#comment-6449 Richard Remington Mon, 01 Feb 2010 18:22:36 +0000 http://docwhat.org/?p=473#comment-6449 I have another thought. As part of the 'boom!' process, I assume you feel that it should be simple to find the bug? Are there ways to ensure that happens? By the way, I love your It's All Text software and use it daily. I have another thought. As part of the ‘boom!’ process, I assume you feel that it should be simple to find the bug? Are there ways to ensure that happens? By the way, I love your It’s All Text software and use it daily.

]]> By: Richard Remington http://docwhat.org/2009/10/smoking-craters-are-good/comment-page-1/#comment-6448 Richard Remington Mon, 01 Feb 2010 18:15:26 +0000 http://docwhat.org/?p=473#comment-6448 This methodology is great, IF the developer is still around to fix his code after a spectacular meltdown. Sadly, one of the more recent places I worked had had a developer create code by the Tandem method and only partly finish. Some things blew up spectacularly, some not at all, and regardless, there was no one with experience, tribal knowledge, or proper documentation to fix anything when it did. :( This methodology is great, IF the developer is still around to fix his code after a spectacular meltdown. Sadly, one of the more recent places I worked had had a developer create code by the Tandem method and only partly finish. Some things blew up spectacularly, some not at all, and regardless, there was no one with experience, tribal knowledge, or proper documentation to fix anything when it did. :(

]]>