comment on

People get got up in the silver bullets of programming. They want the one thing that is going to solve every problem, so they keep looking for the right agile methodology, design pattern, language, or whatever.

The Master knows that all thing have their place. That test-driven development doesn't work everywhere shouldn't be any more surprising than that a screwdriver doesn't work any where. However, programmers are often surprised at, start flame wars over, and discuss ad nasuem which One True Method is the right one.

When you can't write the tests first, you don't. When you don't know the right answer ahead of time, use your best guesss until you do. This sort of thinking is easier when you're not casting about for the magic spell that takes care of everything. :)

--
brian d foy <brian@stonehenge.com>

In reply to Re: When test-driven development just won't do by brian_d_foy
in thread When test-driven development just won't do by Ovid

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Just another Perl shrine
	PerlMonks