there's some thoughts / notes on a paper about computer program structures, links about that here first and perhaps some work on the idea later
- http://www.xpdeveloper.com/xpdwiki/Wiki.jsp?page=MutationTestingTools
- http://ise.gmu.edu/faculty/ofut/rsrch/mut.html
- a session where Jester demonstrates interestingly, http://www.objectmentor.com/resources/articles/xpepisode.htm
- http://www.omnidigm.com/plextest/documentation/WritingMySort.html
- quoting http://c2.com/cgi/wiki?FrequentReleases, which excitingly resonates with Darwin!
- "But wait a minute! Sometimes you have to break something in order to fix it. What about big changes that take a long time to get done?
- It turns out that you don't have to do that as often as I originally thought. One time ChetHendrickson? and I did something that actually took us a couple of weeks. Even now I'm not sure we couldn't have done it incrementally. Since that horrible experience, we have never again found something that couldn't be evolved from where it was to where it needed to be. The effect is wonderful: the system always improves and never goes backward. Believe me, we aren't geniuses who get everything right the first time: but we have learned how to refactor from where we are to where we need to be without passing through Broken on the way back to Go. {Finding the IncrementalPath? requires a developmental sense that starts with believing that there is one.}"
- http://c2.com/cgi/wiki?CodeUnitTestFirst
- (a bit far-fetched in this context but .. http://www.openadaptor.org/about_openadaptor.html )