Much has been written and said about programming in “the zone”. Most articles give you tips on how to get in the zone and keep there. I haven’t found any article though that challenges the usefulness of ‘being in the zone’ (If I have...
The test pyramid is a concept that was developed by Mike Cohn. It states that you should have an appropriate amount of each type of test. In the pyramid he distinguishes different types of tests: * Exploratory tests: Performed manually by a tester * System tests: Executed...
Automated acceptance tests play a vital role in continuous delivery. Contrary to unit tests though, they’re quite hard to get right. This is not only because end-to-end testing is harder than testing single units, but also because of the way they need to be...
In my last few posts I have hammered a lot on simplicity in software. In my first post (Simplicity in software [https://www.kenneth-truyers.net/2014/02/20/simplicity-in-software-what-you-see-is-not-what-you-get/] ) I explained what the difference is between easy and simple code (or hard and complex code)...
In my post on how to simplify code by using composition [https://www.kenneth-truyers.net/2014/06/02/simplify-code-by-using-composition/] instead of an AOP-framework I showed a way of substituting attribute based programming with a more composable paradigm. The result of that transformation will be my...