I asked myself a related question: Why do we claim that our project are agile when they show no sign of agility — the ability to respond to change fast — and fast and also wandered: How do we expect us to be agile if we are stuck in code that we rather should call "Barb Wire Codes" as we are stuck in it.

My answer is an architecture that I would describe as "Contrained OOP" and that in parts feels quite functional as it uses immutable state and unidirectional flow and realizes the message sending by using partially applied functions over methods and classes (which I’d rather describe as the root of all eveil than Java and C++).

Please read on my blog: If It Doesn’t Feel Agile, It Ain’t Agile