December 2008
4 posts
“At the Master of Fine Arts in Software dry run, I did an experiment where...”
– TDD as if you meant it (Keith Braithwaite, Zuhlke Engineering) (Software Craftsmanship Program Selection)
http:/// →
In figuring out acceptance-test-driven design, I think (today) there are two plausible strategies:
ATDD classic: thorough unit test, some form of thorough GUI-avoiding business-facing tests (like with Fit), some amount of whole-product through-GUI tests (like with Watir), and some amount of exploratory testing.
My hypothesis: thorough unit tests, thorough examples written on whiteboard but not...
Emerging Technologies for the Enterprise... →
Exhibitionism in Software Development
One of the values that good Agile teams live by is visibility, taken right to the point of exhibitionism. In this talk, I’ll first explain why that’s a good idea and how it works.
Next I’ll talk about the ideal of radical visibility into code, visibility that allows us to /see/ what neither code nor children in trouble can ever explain:
-...
DABlog Probative Programming: the physical... →
I think you’re onto something with the need for a tighter connection between tests and code. I’ve been running into the problem of that separation myself recently. I have two negative reactions, though:
I never found literate programs particularly readable because they tie you so tightly to the author’s idea of how you should read the program. It’s hard to break out of the...