No design, The testing genes, Sharing thoughts
"Does Agile imply no design? Can the architecture evolve from doing the simplest thing possible? Is up front design good or bad? These questions, it seems, are still very controversial in the agile community. At the Architect Insight Conference in Newport [March 5], several presentations touched upon the topic of design and architecture in agile development." (Gojko Adzic, Agile Architect – Myth or Reality?)
Alberto Savoia identifies the genetics of testing. "I am rooting, of course, for the major victory [where developer testing becomes a standard software development practice], but I am starting to have my doubts, and wondering why progress is so slow. Below is my analysis of what I believe is happening and I’d be very interested in your opinion." ([url=http://www.developertesting.com/archives/month200701/20070126-developer%20testing%20test-infected%20gene.html]Testing Genes, Test Infection, and the Future of Developer Testing[/url])
Srinivas Ramgopal shares his company’s experience with XP and TDD: "We evaluated XP and TDD for 8 months with a new developer (with good previous experience in them) added to the team. The team is a group of seasoned developers but new to agile development. I thought I would share with you the team evaluation with the main intent to know your input based on your experiences with TDD." ([url=http://saloon.javaranch.com/cgi-bin/ubb/ultimatebb.cgi?ubb=get_topic&f=42&t=000820]JavaRanch Big Moose Saloon: TDD/XP – sharing thoughts[/url])Karfai Wusan uses rspec to experiment with Behaviour-Driven Development, and details the step-by-step process of creating a story-editing application (Beyond the Edge of Forever: ruby and behaviour-driven development).
"Working with scaffolding makes it nigh impossible to do test-driven development, whereas working from a UI makes it very, very easy. With scaffolding, what tests would you write first? What is the behavior your want your final product to have? That’s not a very easy question to answer when all you know is the set of models you think your application needs." (Scaffolding’s place)
"Setting up expectations in a mock framework like EasyMock is usually straightforward when dealing with simple types like integers or strings. But from time to time I run into situations when things become more complicated. Consider the following example." (Complex expectations in EasyMock made easy using JSP EL)
Ben Monrog has been thinking of a new agile methodology he calls [url=http://www.benmonro.com/Blog/PermaLink,guid,fe63b91b-48a3-4dc3-95ab-f43eb40c9518.aspx]Demo Driven Development[/url].
Andrew Binstock presents a small review of Agile Java by Jeff Langr, which shows why TDD is a good way to teach Java.
James Carr has matured as a pair programmer: "I’ve been able to first hand experience some of the ways to be a bad partner and a good partner when pair programming. One of my major problems was I had a tendency to either hog the keyboard, or I would do what I like to call Backseat Driving: you let your partner drive, but you dictate exactly what they need to type." (Backseat Driving in Pair Programming)
