Screaming Architecture: on systems

In “Screaming Architecture” Uncle Bob lays out one of the biggest wins by designing to the problem domain, instead of your weapon (ahem.. framework) of choice: “If you system architecture is all about the use cases, and if you have kept your frameworks at arms-length. Then you should be able to unit-test all those use […]

Continue reading →

Anemic Domain Model: on systems

Martin Fowler wrote a piece in 2003 that addresses a subtle anti-pattern – developing your domain model code devoid of behavior. It’s a short, interesting read, that is related to the development of fat controllers in MVCish applications: “AnemicDomainModel”: “In general, the more behavior you find in the services, the more likely you are to […]

Continue reading →

Java on… Heroku!!!!

Heroku adds suport for Java: Heroku for Java. Take note of how simple a basic Java web app can be. Sure it’s not Sinatra or Flask, but it is still mighty simple. Folks who claim that ‘Java is dead’ or that it should die, aren’t facing up to where it shines and what it provides. […]

Continue reading →

CMS and Presentation Systems

stdout.be talks about what Presentation Systems are and what their responsibilities could be in an environment where the CMS is no longer a single system, but an ecosystem in “The Post-CMS CMS”. It’s a great post, and reminds me of how we’ve defined the role presentation systems play in our solution stack. (via @SeanBlanda) Sean […]

Continue reading →

How poor information design led to Waterfall

I just took part in a great 3 day training session with Uncle Bob Martin on TDD and healthy software design. One of the tidbits Bob shared was the history behind the Waterfall methodology that some of us older folks strained against until agile and lean methodologies started to get well known. Waterfall originated in […]

Continue reading →