Yesterday, I found an interesting page (in German) describing some of the most important patterns and practices in software development: http://www.clean-code-developer.de/

Although I’m not a fan of wrist bands (see the linked page to see for yourself), I like the page for its short description of patterns and practices like:

• Don’t repeat yourself
• keep it simple stupid
• single responsibility pattern
• separation of concerns
• interface segregation principle
• dependency injection principle
• Liskov substitution principle
• open close principle
• law of Demeter
• principle of least astonishment
• you ain’t gonna need it
• use a version control system
• issue tracking
• continuous integration
• automated tests
• mocking
• code coverage
• test first
• reviews
• and some more

Architecture, Software Architecture, Clean Code, Design, Development, Patterns, Practices

There are rumors going around on the internet about the release of windows mobile 6.5. Some say that windows mobile 6.5 is never going to be released but other strongly believe that the new windows mobile 6.5 will be released soon.

Not long ago people were blogging on the internet that Microsoft is probably going to focus on windows 7 and it’s integration into the newest mobile devices. But that has not been approved by Microsoft.

Mobile Rumors, Windows, Windows Mobile, Windows Mobile 6.5, Windows7

Often I get asked: Why should I write a test. What should I answer?

My preferred answer is: It’s an insurance to you.
At the time you have tests for your code, somebody else can do modifications on your code and you are sure it still does what it should. Otherwise your test will fail. (Well some people think: Why should somebody else modify my code? That’s impossible, this code is too complex, as it can be modified by somebody else… But this is another story.)

I also like the counterquestion: How can you assure me this code is working?

Testing Testing