Re: How do you write tests if you aren't sure what the result should be?

Hi Amir,

On Feb 17, 2013, at 11:00 PM, "Amir Kolsky" <[email protected]> wrote:

> I meant that the derivation of the formulae that you THEN implemented in TDD
> did not have anything to do with TDD.


Of course it didn't have to do with TDD. It has to do with the laws of physics. It has to do with understanding the problem and is possible solutions. It has to do with understanding what happens if frame rate changes.

If we don't understand those things, our penguin will never fly right, because there are an infinity of possible calculations for his x position and y position. 

These are matters for thought. When we do TDD we don't stop thinking. We stop believing everything we think, and we stop imagining that when we write code, it works as we imagine.

Ron Jeffries
www.XProgramming.com
If another does not intend offense, it is wrong for me to seek it;
if another does indeed intend offense, it is foolish for me to permit it.
  -- Kelly Easterley



[Non-text portions of this message have been removed]



------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/testdrivendevelopment/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/testdrivendevelopment/join
    (Yahoo! ID required)

<*> To change settings via email:
    [email protected] 
    [email protected]

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/