Why Software Plumbers

One of the questions I am often asked in the context of a new business relationship is simply: 'why Software Plumbers?'

The answer harks back to a technical meeting I had at a bank which shall remain nameless. I worked for a software vendor which had just sold the bank a new semi-bespoke application. Eighteen people sat around a huge U-shaped table in a meeting room, tasked with 'making it work'. The Project Director completed his schtick and proposed the usual cringeworthy round of self-introductions.

I was at the far end of the table from where the round began. So by the time it was my turn to speak up, I was aware that round that table we had a Project Director, three Project Managers, six Technical Architects, five Subject Matter Experts, some miscellaneous relationship managers, and me.

My job title at the time was 'Technical Architect'.

When it was my turn to speak, I admitted somewhat sheepishly to being yet another Architect. And then I said, jokingly... 'Although I'm more of a Plumber, really'. What I meant was: I've made this software work many times in many different banks. I'm not here to tell you how you should do it so much as ‌to figure out how we can do it with the resources we have.

Many true things are first said in jest. When you want to build a house from scratch, there is no question, you need an Architect. When your toilet is broken... you call a Plumber. While a theoretical understanding of the problem is important, there is no substitute for years of practical experience doing the job and a willingness to get one's hands dirty.