Clippings

New recording of Architecture without Architects

3 December 2014

In September Michael Tiberg invited me to give my Architecture without Architects talk at the excellent FooCafe. The talk was recorded and the video is available on Youtube.

Right Sourcing book is now published

10 June 2013

SKU-000654545 One of the aspects of our industry that I find most exciting is the amount of change and progress. Sometimes that progress means that even ideas that have come to be considered accepted wisdom need to be revisited. In some of my talks I’ve been arguing for a while now that we need to reconsider the general preference for buying software (over building it).

At the same time Rien Dijkstra was in the process of editing a collection of essays on the topic of sourcing IT and he kindly invited me to contribute my ideas. I was more than happy to accept his offer and I am proud to be part of this collaboration. A preview of my essay has been published on this site as an article series. Now the book is published and widely available.

Building another Hackintosh

23 September 2012

Three years ago, unhappy with Apple’s hardware lineup, I decided to dip my toes into the Hackintosh world. It was a resounding success and the machine I built back then has served me well. So, last month, with Intel’s Ivy Bridge and Apple’s Mountain Lion out, I decided to build another Hackintosh. I have written up my experience in this article.

97 Things Every Software Architect Should Know

6 March 2009

97 Things... Admittedly, I’ve been struggling with the “Architect” title in the IT world. It is not that I think there’s no role for architecture, far from it, but too often I’ve encountered architects who focus too narrowly on architecture, losing track of the realities of actual software development and the context in which the software will be used. I wonder, if there was no “Architect” title and people who are responsible for architecture would be called guide or coach or tech lead, or just the senior developer, whether things would be better.

About a year ago, in a discussion about architects, rather than trying to define what an architect is or does, we looked at what he or she should know. We expressed our ideas as mini-essays, strictly limiting ourselves to one per essay, and it turned out that, at least to my surprise, there was a lot of agreement; maybe because we hadn’t come up with hard and fast rules but with ideas and guidelines.

Luckily Richard Monson-Haefel was part of that discussion and he had the resolve and means to make our thoughts more widely available. Our list of the 97 things every architect should know was collected and refined on this wiki, and is available under a creative commons license. For a more convenient read it has now also been published as a book by O’Reilly. As expected, the discussions have begun.

Guardian podcast

4 May 2008

Of the many projects I have worked on the rewrite of the Guardian website is certainly a highlight. And in this case I can even speak about it in detail. In fact, Mat Wall from the Guardian and I presented some of our experiences at several conferences, and now the Software Engineering Radio has published a podcast in which we talk about this project.