On day two of VMworld Barcelona 2017, our team of intrepid podcasters were able to catch up with Chief Operating Officer of Customer Operations, Sanjay Poonen, for a chat about life, careers, cloud architecture, VMware strategy and the startup space!
It was a great conversation and clear to see how passionate Sanjay is about the organisation, but more importantly, the people around him. He ended the podcast with a few nuggets of career advice which I think are well worth taking on board for anyone, regardless of seniority or time in the industry. The episode is well worthwhile a listen for this alone!
Once again, Kev, Ather, Amit and myself were there in person, with Gareth remotely dialled in from the UK via Zoom, albeit via a rather dodgy wifi connection at our end!
We were fortunate enough to sit down with both Sanjay and Pat Gelsinger at the event (find interview post here!). It’s great to see senior leadership at as huge an organisation as VMware taking the time out of their insane conference schedules to involve themselves in community initiatives, such as the Open TechCast!
Community engagement is one thing I think VMware continues to do better than most organisations in the industry. It’s probably (at least in part) VMworld continues to attract larger audiences every year, even when other public cloud vendors are taking such large chunks of attention and market share.
Finally, massive thanks again to Sanjay for taking the time to hang out with us! It was a blast!
If you want to catch this extra-special episode of the Open TechCast, you can tune in at:
The subject matter of this post is a startup of sorts and was triggered by a conversation I had with an industry veteran a few months back. By veteran of course, I mean an old bugger! 😉
It is an entity which begins its journey sourcing a target market in the tech industry and spends day and night pursuing that market to the best of its ability.
It brings in resources to help meet the key requirements of the target market; some of those resources are costly, and others not so much.
Occasionally it hits a bump in the road with funding and potentially needs to find other sources of investment, and may go through several rounds of funding over the course of a number of years. Eventually it gets to a point where the product is of a decent quality and market value.
Then it does a market analysis and discovers that the market has shifted and if the entity does not pivot or indeed re-skill, they will become irrelevant within a few short years.
I am of course talking about the career of an IT professional.
Though I may be slightly exaggerating on the becoming irrelevant quite so fast, we certainly all made the choice to follow a career in one of the fastest moving industries on the planet. We have no choice but to continue to develop and maintain our knowledge, in order to keep driving our careers forward.
As a self-confessed virtual server hugger with a penchant for maintaining a pretty reasonable home lab, I enjoy understanding the detailed elements of a technology, how they interact, and acknowledging where the potential pitfalls are. The cloud, however, is largely obfuscated in this respect; to the point where many cloud companies will not even divulge the location of their data centres, never mind the equipment inside them and configuration thereof!
That said, those of you with a keen eye may have noticed a shift in my twitter stream in the past year or so, with subjects tending towards a more public cloudy outlook… Talking to a huge range of customers in various verticals on a regular basis, it feels to me that a great many organisations are right on the tipping point between their current on-premises / dedicated managed services deployment models, and full public cloud adoption (or at the very least hybrid!).
It’s hard to believe that companies like AWS have actually been living and breathing public cloud for over ten years already; that’s almost as long as my entire career! In that time they have grown from niche players selling a bit of object storage, to the Behemoth-aaS they are today. To a greater or lesser extent (and for better or worse!), they are now the yardstick upon which many cloud and non-cloud services are measured. This is also particularly the case when it comes to cost, much to the chagrin of many across the industry!
To me, this feels like the optimum time for engineers and architects across our industry (most definitely including myself) to fully embrace public and hybrid cloud design patterns. My development has pivoted predominantly towards technologies which are either native to, or which support public cloud solutions. Between family commitments, work, etc, we have precious little time to spend in personal development, so we need to spend it where we think we will get the most ROI!
So what have I been doing?
Instead of messing about with my vSphere lab of an evening, I have spent recent months working towards certified status in AWS, Azure, and soon, GCP. This has really been an eye opener for me around the possibilities of designs which can be achieved on the current public cloud platforms; never mind the huge quantity of features these players are likely to release in the coming 12 months, or the many more after that.
Don’t get me wrong, of course, everything is not perfect in the land of milk and honey! I have learned as much in these past months about workloads and solutions which are NOT appropriate for the public cloud, as I have about solutions which are! Indeed, I have recently produced a series of posts covering some of the more interesting AWS gotchas, and some potential workarounds for them. I will be following up with something similar for Azure in the coming months.
Taking AWS as an example, something which strikes me is that many of the features are not 100% perfect and don’t have every feature and nerd knob under the sun available. Most seem to have been designed to meet the 80/20 rule and are generally good enough to meet the majority of design requirements more than adequately. If you want to meet a corner use case or a very specific requirement, then maybe you need to go beyond native public cloud tooling.
Anyhow, that’s enough rambling from me… By no means does this kind of pivot imply that everything we as infrastructure folks have learned to date has been wasted. Indeed I personally have no intention to drop “on premises” skills and stop designing managed dedicated solutions. For the foreseeable future there will likely be a huge number of appropriate use cases, but in many, if not most cases I am being engaged to look at new solutions with a publicly cloudy mindset!
So for those of you who have been following my meandering mutterings for a while, you may know that I’ve been working as a Solution Architect for the UK arm of a pan European managed service provider over the last few years.
In the past I have worked in several different types of IT environment, from internal IT at a large enterprise, to working as an outsourcer for two very large vendors. Being at a service provider is really interesting as you get to work with many different customers, with many varying requirements, and help each one to find the right solution for their business. I have found it to be such a cool part of the industry, I am keen to continue working in it for the foreseeable!
As such, as of next week, I am very excited to be starting a new role as a Solution Architect for Rackspace Ltd in the UK, based out of the (rather awesome) main office in Hayes!
Before anyone asks, I should note that this does not mean that I will suddenly forget my VMware indoctrination (should that be inculcation or institutionalisation? 😉 ), and go all in on OpenStack. That said, it is actually one of the things I am most looking forward to learning more about.
Coincidentally, not long before being approached about the role I was actually tweeting about the growing popularity of OpenStack. This seems to me to be a great time to learn more about it, especially with things like VIO becoming more and more popular, helping enterprises who might otherwise be reluctant to jump on board without enterprise levels of support.
Are we right on the edge of mass #OpenStack adoption? Many large enterprises now paying it attention behind closed doors… #RealWorldIT
With any luck, I may even get the time to write about OpenStack here on the blog, but of course, it will not be the only subject for my posts! I remain fiercely vendor agnostic, just at a larger independent organisation! 🙂
On that vein, fingers crossed I will still be able to put the same amount of time aside of an evening to maintain the blog and attend events such as Tech Field Day in the future, but for the next few months at least things may be a little quieter. I will be head down, brain-sponge engaged, learning all about the hundreds of products Rackspace provide, meeting my new colleagues and generally making a nuisance of myself with newbie questions!
Written by Gene Kim, Kevin Behr, and George Stafford, it is told as a first-person narrative from the perspective of Bill, a middleware team manager who is promoted into a senior IT management role for a business in jeopardy. Through his experiences and a guiding hand from another key character, together we work through the problems facing the business, the IT department and the individuals within.
The story is told in an easy to read, informal style, and I made quick work of it over the course of just a few days. I really enjoyed it on numerous levels:
I recognised every single character in the book as somebody I have worked with (or indeed currently work with!). I guarantee you will feel the same!
The book was pretty well written, and the story arc itself was compelling. I was really rooting for Bill to succeed in his endeavours! (But did he? You will have to read the book to find out!)
The authors obviously have a great sense of humour! Quotes such as “Show me a dev who isn’t crashing production systems, and I’ll show you one who can’t fog a mirror. Or more likely, is on vacation.” had me laughing out loud on the train in front of other passengers!
The book is approachable and not elitist. You could pick it up as a cable monkey or an IT director (or maybe even a Sales person!!!), and relate to the concepts and methods described.
I learned a huge amount about different methods for handling and improving processes around WIP (Work in Progress), such as the Theory of Constraints or the use of Kanban boards (I am currently testing this with my pre-sales customer workloads using Trello, but I’m told Kanbanize is also very good). Resilience Engineering (think Netflix Simian Army) and numerous other techniques are also covered, along with the overarching “Three Ways” (very Zen!).
I actually picked up a few key tips which could be applied directly to my pre-sales design and requirements gathering workshops with my customer stakeholders.
Finally, it didn’t feel “preachy”, which is always a risk when trying to sell an idea / concept as your main theme and I was initially concerned that the book would be ramming DevOps culture down my neck throughout. This could not be farther from the truth, and the full DevOps concepts do not come into play until the story is almost complete. There are many lessons to be learned throughout the story, which could be applied to any organisation!
Here are another few choice quotes from The Phoenix Project, both humorous and insightful:
“The only thing more dangerous than a developer is a developer conspiring with Security. The two working together gives us means, motive, and opportunity.”
“How can we manage production if we don’t know what the demand, priorities, status of work in process, and resource availability are?”
“You just described ‘technical debt’ that is not being paid down. It comes from taking shortcuts, which may make sense in the short-term. But like financial debt, the compounding interest costs grow over time. If an organization doesn’t pay down its technical debt, every calorie in the organization can be spent just paying interest, in the form of unplanned work.”
“On the other hand, if a resource is ninety percent busy, the wait time is ‘ninety percent divided by ten percent’, or nine hours. In other words, our task would wait in queue nine times longer than if the resource were fifty percent idle.”
In case you hadn’t felt like I was positive enough about The Phoenix Project yet, I would say that this book should be provided as mandatory training to every person working in every IT department today, from the guys plugging in cables to the CIO!
If you do read and enjoy the book, I highly recommend also reading The Goal by Eliyahu M. Goldratt. I was a little surprised, to say the least, that this appears to be a very similar story, following a similar arc and some almost identical characters to The Phoenix Project. That said, I am half way through it at the moment and still thoroughly enjoying it, though I am not too worried about missing the movie version!
The Goal delves even deeper into the Theory of Constraints and explains some of the tools we can use to mitigate, bypass or remove constraints in a system. All of these tools and methods can be applied as easily to IT as they can to production lines, which (without stating the bleeding obvious) is exactly the point of The Phoenix Project!
Anyway, if you want to do yourself a favour both in terms of your career development, but also a really compelling story and a thoroughly decent book, you could do a lot worse than spending £5 on the Kindle Edition of The Phoenix Project!
Where To Get Them
For anything technical, I like to buy ebooks these days for both portability and the fact that I wont be chopping down trees needlessly. Both of the above titles are available very inexpensively on Kindle: