Compare the two trees below. In both cases the goal is to have an application with two independent modules (frontend and reporting), and one shared/common module (domain). The code in … Continue Reading →
Category Archives: Methodology
Dry parameter names
How often do you see code like this, especially when using dependency injection, single-responsibility principle, and other “good practices”? 1 2 3 4 5 class FriendsTimelineReader(userFinder: UserFinder, userStatusReader: UserStatusReader, statusSecurityFilter: … Continue Reading →
Veripacks 0.1 – Verify Package Specifications
Using some free time during my Christmas & New Year break, I worked on a new project, which implements some of the ideas from my earlier blog “Let’s turn packages … Continue Reading →
Frameworks vs Libraries as Inheritance vs Composition?
For quite some time inheritance was the dominant model of structuring programs in OO languages like Java. Very often it was used as a mechanism for reusing code – “common” … Continue Reading →