This post originated from an RSS feed registered with Agile Buzz
by James Robertson.
Original Post: Edit Continue vs. Test-Driven Development
Feed Title: Cincom Smalltalk Blog - Smalltalk with Rants
Feed URL: http://www.cincomsmalltalk.com/rssBlog/rssBlogView.xml
Feed Description: James Robertson comments on Cincom Smalltalk, the Smalltalk development community, and IT trends and issues in general.
You now have a situation where a simple unit test%A0is only a couple function%A0calls away from any bug.%A0 Compare to the Einstein case I mentioned earlier, and you'll see that complex repro scenarios are comparitively rare.%A0 You can reproduce the faliure in seconds - just run the unit tests.
When that cycle is so short, E&C doesn't help nearly as much.%A0
The "Einstein" reference is in relation to an internal to MS view on various developer types; I'll have to post on that at some point. Here though, I see something interesting - MS is only just starting to support the kind of immediacy (edit and continue) that Smalltalk supports so much better than they do - and their developers just don't see the value. Amazing. I used a TDD approach when developing my MarkupHelper (for the blog posting tool), and it was so much easier to do since I could look at stuff in the debugger and change it right there - without having to run back to some different tool. Interesting difference in viewpoints at the very least...
Previous Topic
