Stephen Freeman Rotating Header Image

May, 2005:

Hack your way out of writer's block

An excellent piece at “43 Folders”:http://www.43folders.com/2004/11/hack_your_way_o_1.html. In one of the comments there’s a link to an article on “Writing clearly on deadline”:http://www.copydesk.org/words/writingclearly.htm which includes some interesting ideas for Agile teams:

bq. Decide early what your minimum story is, the story that answers the basic who, what, when, where questions. This is the story that meets basic levels of journalistic competence and allows you to keep drawing a paycheck next week.

bq. Decide early what your maximum story might be, the story that readers will be talking about at work and in coffee shops the next day. This is the story that your editors and readers will remember, that marks you as a star performer. This story may answer difficult how, why, so-what or how-much questions or it may address the who-what-when-where questions in greater depth. The maximum story will have such enticing elements as setting, plot, characters and dialogue. You are looking for elements might make this story especially memorable.

bq. On deadline, you want to identify immediately the potential sources who could provide the information for the minimum story and get the information from them as quickly as possible. Then you zero right in on the sources who might provide the maximum story. Maybe you can’t get the maximum story on deadline. It might be a second-day story or a Sunday follow-up. But go for it. If you don’t land the maximum story, you’re likely to gather material that will improve on the maximum story.

For Mac users, there’s also a link to this “really cute application”:http://alphaomega.software.free.fr/typewriterkeyboard/Typewriter%20Keyboard.html

jMock constraints belong in jUnit

Joe Walnes has “written up”:http://joe.truemesh.com/blog//000511.html the idea that jMock constraints should be used in jUnit assertions. It reads better and is more flexible.

I’m glad he’s written up such a nice explanation because some of us have felt for ages that this infrastructure belongs in jUnit, rather than in jMock, but it isn’t going to happen.

Happily for .Net developers, the NUnit committers are more accomodating and have taken on some of these ideas from NMock.

Lobby your jUnit committers now!


Update, just added an _assertThat()_ method to the “jMock”:http://www.jmock.org library. It should find its way into the next release.
(more…)