Recent Articles
November 5, 2011
Bob and Alice sit in a cubicle at the end of the floor. For much of their working day they are pissed off. They are forced to do their job using a tool implemented by The Project some years ago. The Tool was an over-complex inappropriate hulk when it was selected. The Tool is made by The Big Vendor. We've all heard of The Big Vendor. They market The Tool to many industry segments and have a specialist pre-sales team for each segment. The Tool was very expensive. Because of its complexity it's hard to do simple things quickly with The Tool. To work around these inadequacies various shell script ...
[more]
July 30, 2011
Welcome to part two. Last time we looked at the experience of getting a NoSQL product accepted in an enterprise environment. Assuming you got through that, the next step is to do something useful with it. Like any tool, you will only get good stuff out if you know how make the best of it. In this case that means not treating it too much like a relational database and understanding the internal nuances.
For our particular set of requirements we chose MongoDB. We tried Oracle first but either the data model became too unwieldy, which slowed down development, or we were looking at blobs, which ...
[more]
July 30, 2011
Time flies - it was nearly two years ago that I wrote 'Strained Relationships', an article extolling the potential benefits of NoSQL data stores. My main point then, and now, was that certain features of the new wave of non-relational products looked a promising solution (in part) to improving speed-of-change in large enterprises. Sadly, too many articles in the NoSQL space still focus their attention on drooling fanboi speed and whilst it's true that NoSQL products are generally faster than their relational cousins (as long as you are prepared to shift designs and mind-set accordingly) we are ...
[more]
June 5, 2011
I noticed last week just how many half-written articles I have queued up for completion. Postwise, the last twelve months has been heavy on ideas but light on completion. Sorry about that. Unless you think my stuff sucks in which case: "you're welcome". It's been a very busy period and writing time has been hard to find. But when I look at some of those half-formed works I see that they lack a narrative sense of beginning, middle, and end. Ideas are great but I find it hard to summon up the enthusiasm to finish them unless I am also caught up in the story that brings them to life.
This one ...
[more]
May 29, 2011
Last time, I was talking about what I consider to be the general lack of a crisis in software development. And it got me thinking - if there is no crisis in software development, no inherent flaws in our tools or our methods, then there must somehow be a way to convey the appropriate use of these tools and methods in order that everybody could get it right every time.
Ah ha, I thought. A book. A book entitled "The Secret Sauce". A book that will make me one .. million .. dollars. I can buy an island, with my own mini-me, surrounded by frickin' lasers.
But of course there is no book. There' ...
[more]
January 30, 2011
So I have a question, or at least I think I do, because maybe the answer is obvious and any sense of there being a question is redundant.
Why do so many articles on software development these days (and for some time) start with outlining how truly awful, and late, and expensive it always is?
I've said it too, often. But it's getting boring. Statistically, if you were to parachute into a randomly selected IT development project today, the odds that it's building the wrong thing, or the right thing badly, or that it's hugely late and has cost more than planned are overwhelming. We know that. S ...
[more]
November 13, 2010
If there's one aspect of enterprise IT guaranteed to get the dander up it's Standards and Governance. Some time ago I wrote a short piece on governance called The Governance Apparition making the point that governance should never really be seen as separate and distinct from 'doing things'. If a company has a process for 'doing things' and an internal body (usually architecture) tries to 'govern' the outputs of that process the governance will fail.
It will fail because it's almost impossible to avoid making governance look like a hindrance to delivery. Delivery is hard enough; nobody appreci ...
[more]
May 17, 2010
To a man1 with a hammer, everything looks like a nail. A well-worn phrase used to alert us to the dangers of getting so caught up with one product or technology that, whatever the problem we are trying to solve, our answer is always to use it. On the surface it seems like good advice. You wouldn't want to artificially restrain your efforts by choosing a completely inappropriate technology, would you?
But how would you know? Delivering good software is never easy. If it was people like me wouldn't get to piss and moan on the internet about how hard our lives are.
For example, let's say you ...
[more]