In our new project, we've decided to use FitNesse with slilm. All in all, slim is an improvement over fit. The thing I like most is the error messages when running tests. These are now much clearer than with fit. The fixtures are now plain old objects (that's poo -- you can call them pojo, poco or even pono for all I care). So no dependency anymore on fit. Slim is also supposed to run faster, but right now our project is not really big enough to notice the difference. There's two things I don't like ......
We're nearing the end of our second iteration on a new project. I started out by setting myself a few goals to explore. I'd like to write them down here, so I can come back in a few months to see what remains of them. You're welcome to comment on these goals.Overall- readable, intent revealing software- DRY, YAGNI, BOYSCOUT et all...Entities:- IAggregate root has interface- No ID (I'm not sure if I can pull this one off with NHibernate)- No (public) setters except for things like name, description, ......
Note to the one reader I have (Hi mom!): I accidently deleted this post, so this is a repost. I’ve just started a new initiative in our company: a coding dojo. I first saw this last week at the XP days, and I loved every minute of it. Emmanuel Gaillot introduced us to this idea with a simple challenge: compare poker hands. The implementation was written in Haskell from scratch, using TDD and Baby Steps. As Bob Martin mentioned: the beauty of this was that most of the attendees did not know Haskell, ......