I just figured out why callback style APIs are harder to test (and harder to deal with in general). It’s because they break one of the essential ingredients of a hexagonal architecture: the middle hexagon should be independent of the adapters. Here’s why… In order to use a callback API, one or more of our… [Read more…]
Warning: academic theorizing and hypothesizing follow. Oh, and half-baked pontification. I just finished refactoring reek to drive in a major new chunk of functionality (configuration files) which I’ll release soon, when I’ve had time for some thorough testing. The refactoring needed to accommodate the change was huge, occupying much of my free time over the… [Read more…]
Dave Verwer at NWRUG has been crazykind enough to invite me to re-run a version of my hexagonal architecture workshop this month at the MDDA. This is the session that, two years ago, had seventy of the world’s leading agilists standing on one leg. If you’re in Manchester on the evening of November 20th, why… [Read more…]
Is there really anything to debate about Data Classes? And can hexagonal architecture clarify the situation?
In which I explore the impact of metaphor on system architecture
I spent an enjoyable day last week at XPdays Benelux in Rotterdam. I ran a couple of sessions, attended a couple more, and met up with friends old and new
In which Brian Marick recommends designing your own API to the filesystem
My Jidoka and Hexagonal Architecture sessions have been accepted for XPday Benelux 2005 in Rotterdam this November
Last month Alistair began using a new name for the Hexagonal Architecture pattern
Never throw an exception. And if someone throws one at you, catch it immediately and don't pass it on
March 16, 2009
5