Architect your Career
If you’ve ever watched the TV show Grand Designs you’ll know that one of the mantras of the host Kevin McCloud is that the builder should not be the architect or the project manager. Every time there’s a self-build project and the couple take on more than their capabilities his first piece of advice is to get a dedicated architect or project manager. And he’s normally right.
Well, why don’t we take the same principle to our careers. We are essentially all self-builders. We’re the people digging the foundation, laying the blocks, installing the plumbing and electrics. All while learning on the fly. Exactly like a career. Sometimes when we’re caught up in the minutiae of the day to day things it’s hard to step back and take a 10000 feet view of where things are at and where they can go. As solution architects this is exactly what we have to do. Look at the vision, the requirements, the constraints, the capabilities and what interfaces need to be taken into account.
Where this this all start?
Towards the middle of last year the company I worked with underwent a major organisational restructure within the IT department. The reasons for the change were I believe justified, as the company grew through acquisition they needed to be able to ensure 24 x 7 global support and have the ability for the regional teams to be in constant communication and collaboration. The goal was to drive standardisation across all sites and in turn drive down costs to deliver IT services. Prior to this each primary site, a total of 9 globally, worked in their own silos with their own budgets. The vision was needed but as with all restructures there are some casualties. Some are desired and others are just unintentional fallout. Following the acceptance by senior executives there were some immediate resignations at the mid-management level which were expected. The delivery of the new restructure dragged on however and led to a number of senior engineers leaving too. Including me.
We’ve all heard stories of hoarders. That one guy in the neighbourhood that has two cars, a lawnmower, a boat, two dog sheds, an engine from a vintage car, a second rusted engine from a vintage car, some bales of hay and what looks to be a Salvador Dali custom one of a kind sculpture in their front garden. There’s even TV shows about these guys. I honestly believe some of the most under-represented hoarders are those that work in IT. In some cases they should actually be museum pieces. Everyone I know has battle scars of having to deal with ancient relics from a bygone era that is hosting the most critical application for the entire company and hasn’t been patched in 20 years because Jim that installed it but has since retired and no one else is will to risk it. What if it never comes back up? It’s not under a support contract. How is it that IT systems are still being bound with baling twine (probably taken from your neighbourhood hoarders hay bales) and refurbished, bought from e-bay, hard disks? Any worst of all, it’s generally accepted as standard practice in some places. I’ll never forget being ask by the finance director if we could just buy a new EMC Clariion from ‘the internet’ rather than go through a proper procurement process with EMC directly. “Shur isn’t the internet cheap.” Yes boss it is but…..
So to understand this mentality of not wanting to change and hoarding old equipment in data centers in a large part to justify their existance I have take a look at what a hoarder is and also what it is not.
What a hoarder is not:
A hoarder is not a collector. A collector has a sense of pride about their possessions and take pleasure in showing and talking about their possessions. Collectors tend to keep their possessions organised. A hoarder on the other hand will generally experience embarassment about their possessions and feel uncomfortable when others see them. Their possessions take over the functional living space and they often incur great debt to satisfy their hoarding needs.