Change is inevitable. In fact, this is the only constant. It applies to the evolution of species, human culture, technology and the weather. Apparently it is especially applicable to everything associated with software development. Agile evangelists want us to embrace change. I think what they mean is we need to plan for change and allow changes in every part of the system that is under development. This means that schedules should not extend too far into the future and that technical decisions should never be fixed or final, before the project ends. In effect this promotes a very constant change management, where changes are continuous but small in stead of big and interrupting.

(more...)

Filed under Agile | 2 Comments »

I recently read a book called ‘Design Rules, Vol. 1: The Power of Modularity’ written by Carliss Y. Baldwin and Kim B. Clark. It was pointed out to me by Adrian Colyer during the excellent AOP training mentioned in the previous post.
The title ‘Design Rules’, note the plural ‘Rules’, is something of a misnomer. In fact the authors describe only a single rule, albeit a very important one. They argue that the computer industry started its spectacular growth after clever engineers at IBM decided to break up the design of the 360 family into a set of modules that depended on each other through interfaces.
(more...)

Filed under Java | No Comments »

How to use AspectJ to check your code in combination with maven2?

A couple a weeks ago me and some colleagues took a two day course in AOP. The course was given by the excellent teacher Adrian Colyer. In this short blog I want to show you a very nice (not well known) feature of AspectJ and how you can integrate AspectJ in your build using the maven2 plugin.

(more...)

Filed under Java | 1 Comment »