Freedom to focus on one thing at a time.
- what am I building?
- what defines success--how will I know when the code works?
- how do I describe that? how will I interface with that?
- how do I code that?
- does it work?
- did I inadvertently break anything else?
- are there opportunities to improve the design?
- are there opportunities to improve clarity for us all?
- what's the next small increment that will move the system forward?
That's a lot of stuff to remember. And yet the ingrained cycle of TDD
means I don't ever forget what
questions
are or where I am.
Freedom to think.
Cheers,
Jeff
|
| Jeff Langr / +1-719-287-4335
|
|
|
|
|
|
toggle quoted message
Show quoted text
I'd like to build on this in addition to echoing it.
Everyone,
feel invited to join in. I'm asking everyone and not only George.
Which
freedoms? Why do you care? What do those freedoms give you?
I
have noticed these kinds of freedom:
- freedom
from chasing after silly mistakes
- freedom from having to
"get it right" the first time
- freedom from agonizing over
design decisions
- freedom from the blank page
Most
of all, I enjoyed the freedom from thinking that I had to "be born with
it" to design software systems well. This is the freedom I wish most to
share with the most people. And that's why I teach TDD.
-- J.
B. (Joe) Rainsberger :: ?::
::
Replies
from this account routinely take a few days, which allows me to reply
thoughtfully. I reply more quickly to messages that clearly require
answers urgently. If you need something from me and are on a deadline,
then let me know how soon you need a reply so that I can better help you
to get what you need. Thank you for your consideration.
--
J. B. (Joe) Rainsberger ::
::
::
Teaching
evolutionary design and TDD since 2002
