Thought Provokers From Python’s Guido Van Rossum and Clojure’s Rich Hickey

At Strange Loop 2011 Clojure’s Rich Hickey gave a presentation (video) on programming and simplicity that rankled some feathers and triggered a heated discussion at reddit. Duncan McGreggor, decided to contact Python’s Guido Van Rossum to interview him about his keynote talk at PyCon US 2012 (video), specifically his thoughts on callbacks.

Continue reading →

A James Shore 2006 Post My Favorite Design Read So Far in 2012

James Shore’s post in 2006, “Quality With a Name” summarizes clearly what I try and express and practice in my systems design work. This is something to not only read and bookmark, but print out to remind folks who are building systems what exactly is good software design. A good software design minimizes the time […]

Continue reading →

A retrospective on “No Silver Bullet” in Software Engineering

OOPSLA held an all-star panel (including Dave Thomas and Martin Fowler), earlier this year, on the must-read paper from Fred Brooks (included in the must-read book “Mythical Man-Month”) “No Silver Bullet — Essence and Accidents of Software Engineering”. Read the paper. Then read the panel’s transcript. WikiWikiWeb: No Silver Bullet

Continue reading →

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 →

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 →