In my post about software simplicity [https://www.kenneth-truyers.net/2014/02/20/simplicity-in-software-what-you-see-is-not-what-you-get/] I talked about how we introduce complexity in software without realizing it. In this post I want to discuss a pattern that allows you to get rid of the complexity introduced...
As software developers we put a lot of focus on simplicity. And rightly so, because making code readable and understandable keeps it from becoming a maintenance nightmare. Simplicity is often confused though with how many lines of code there are. When you use lines of...
In my previous post “Why choose DI Interception over Aspect Oriented Programming?” [https://www.kenneth-truyers.net/2013/05/16/why-choose-di-interception-over-aspect-oriented-programming/] I explained my preference for DI interception over AOP. I received a lot of comments on this (especially on reddit) which pointed out some errors....
Note: I have posted a follow-up post with some corrections to this post, thanks to some comments made on Reddit: A brief comparison of AOP techniques [https://www.kenneth-truyers.net/2013/05/27/a-brief-comparison-of-fundamental-aop-techniques/] Let me start with saying that in this post I will...
Dividing an application in N layers is considered a standard and a best practice. It is often thought that this automatically creates a decoupled application. However, just creating layers doesn’t make your code loosely coupled. A typical N-layer application Let’s take a simple...
