Thursday Oct 20, 2016
Tuesday Oct 11, 2016
Published articles at Baeldung part 4
As technical editor at Baeldung I have edited the following articles this week:
Wednesday Sep 28, 2016
Saturday Aug 13, 2016
Friday Jul 15, 2016
Published articles at Baeldung part 1
As technical editor at Baeldung I have edited the following 4 articles this week:
Sunday Jul 10, 2016
The death of continuous delivery and object orientation?
I found the following articles to be very interesting:
Friday May 02, 2014
Feature teams versus component teams
In the book "Scaling lean and agile development" by Craig Larman and Bas Vodde, chapter 7 is devoted to the explanation why scaling up with feature teams is to be preferred over scaling up with component teams. In case you are stuck with the latter and cannot change to feature teams, this writing on ScrumAlliance.org explains how to cope with the latter situation.
Link to a successful GIT branching model
Here at info.nl, we are using this branching model, which is a must read, as far as I'm concerned! As far as GIT rebasing is concerned (which is assumed a prerequisite in the former article), this page explains it well.
Thursday Jul 19, 2012
Wednesday Jul 18, 2012
CQRS white paper
Together with Koen Molkenboer, I have written a white paper, titled "A radically different approach to enterprise web application development". In this paper we assert that the reason that the development of enterprise web applications often exceeds both time and budget limits is often two-fold: on the one hand layered web application architectures often pose developers as well as architects many technical challenges, on the other hand a proper implementation of an iterative development methodology often fails since a lack of communication frequently hampers an optimal cooperation between business and IT. In this paper we propose a radically different approach to traditional web application development and the n-layered architecture that is often unconditionally associated with it, as well as the well-known gap between business and IT. The technical part of our alternative approach is based on a comprehensive domain-driven design that is fully persistence ignorant. This is realized by an implementation of an architectural pattern: command query responsibility segregation (CQRS). An improved communication and subsequent improved collaboration between business and IT is established by the development of a ubiquitous language, which in turn is enabled by the aforementioned domain-driven design.