A related post on space-based architecture was published a couple of weeks ago. It was going to be a one-off but I was at the inaugural Gigaspaces User Group in London recently, and a couple of things occurred to me between presentations that I thought worth mentioning. So there are two extra articles to come (this is the first). Perhaps it’s not a conventional place to start, but the idea for ...
Here’s how the story goes. There’s a meeting of all the big cheeses at our favourite company, Gristle and Flint. It’s quite usual for the other directors to vent their frustrations at the CIO - the desktop hardware refresh is running late, IT personnel costs are on the rise, the web site was down all weekend, new budget requests are coming in to support stuff with weird names like ‘middleware’...
Creating software in the corporate environment is a complex business and complexity is a wonderful breeding ground for risk. There are two types of risk that need to be dealt with: acquired risk and inherent risk. Acquired risk will be the subject of a later post. It’s the quid pro quo of software development - choose the bleeding edge, expand your scope, try something experimental, and you’ll...
How is it that you can sit through a film, even a fairly tedious one, that last ninety minutes to two hours, and yet frequently become arse-numbingly twitchy less than ten minutes into a PowerPoint presentation? I grant you, even fairly dull movies are vastly more interesting than most presentations on SOA governance, but should they be? You get paid to do something during the day that for mu...
This article is something of a preface for all other articles and, as with other posts, will be updated from time to time.
The intention for the site is to create a kind of holistic view of what can be done about the current malaise in software development. That there is a problem is in ...