This page is meant to be a place to share techniques that we think are useful to us and we think that it would be a great idea to share these with the community.

• Writing cleaner JUnit tests in Java – Placing the verbose parts of the Unit test away form the method name for improved readability

Not sure how to spell this out, but I will give it a try. We (at NexWerk) have embraced very much the ideas from Eric Evans's book Domain Driven Design. But what does this really mean? Eric Evans book shows you how you should keep constant conversation with your customer to come up with the design of your system. This design should be as close to the domain that is being developed as possible, if possible without translation. And there is where we have seen the key to it.

If one of the paramount issues in the code is that it should be clean, well factored, etc, etc we would like it to be readable by the customer. Only that way we know that the translation of the problem area into the code has not suffered from a translation. I am still trying to find the correct words for this and I hope to come up with some better explanation with some examples soon…

— Enrique Comba Riepenhausen 2009/04/15 07:06