Skip to main content

Where Were You When...

Where were you when

...Hank Aaron hit his 715th home run?

...Steve Jobs introduced the first iPhone?

...Felix Baumgartner jumped from 39km in space and parachuted to Earth while televising it?

Mmm...soda!
My wife and I have had this long-standing debate about whether drinks with Aspartame should be consumed.  She says no, but I say yes because I don't want the added sugar since I'm overweight as it is.  (Nevermind the options of not consuming the drink in the first place because then I'd drink beer instead and that's no better for my waistline.)  So once while consuming one of my favorite beverages - San Pellegrino Limonata - I read the list of ingredients to see which type of sweetener was present.  It was sugar.  I lost.

"Remember when there was this huge backlash about High Fructose Corn Syrup?" I asked her, in hopes of avoiding discussing the fact that I was drinking something with sugar in it.  At that point, we both acknowledged that during that backlash companies reacted in one of two ways:
  1. They fought back and tried to convince the general public that High Fructose Corn Syrup was just like sugar, didn't result in elevated risk for obesity, diabetes, etc.  We all saw the advertising campaign from the corn growers that highlighted this.

  2. They modified their recipes to use cane sugar, Agave nectar, or something else.
When talking to executives at my customers, I've often rallied behind the statement by Gartner in 2014 that companies either think like a technology company or lose their "first mover advantage."  (I like to paraphrase that as "constantly innovate or rapidly become irrelevant.")  For companies looking to avoid being this equivalent of the Titanic DevOps seems like a viable pivot, and yet this has become the veritable albatross around the neck of many CxOs who want to adopt DevOps but completely fail to do so.

What gives?  One of the tenets of DevOps is the CALMS initialism.

Culture
Automation
Lean (process engineering, that is, not the avoidance of sugary beverages)
Measurement
Sharing

None of these items are things that happen overnight, especially cultural support for the evolution to a DevOps mindset.  The biggest problem with the latter is the inability for organizations to overcome the way of thinking that encouraged IT silos, the "it's not my job" mentality, etc.

Think High Fructose Corn Syrup.

When the backlash against that happened, companies that were able to change the way they created their products enjoyed a huge (my guess, not backed up with empirical data of course) bump in top line revenue because this issue was "top of mind" for many consumers who were consumed with creating a more healthy lifestyle.  For the companies that stuck with the old ingredient, they certainly didn't "rapidly become irrelevant," but I can assure you that even to this day I still check the ingredients list and avoid products with High Fructose Corn Syrup in it whenever possible.

DevOps is a journey to be sure.  But the journey will pay dividends for years to come, and so it is an investment that is worth every penny of sweat capital that you will invest.

Popular posts from this blog

Time to Level Up!

With the recent news out of Salesforce and Oracle, it’s easy to understand why folks affected by layoffs might feel discouraged. Not only are they leaving companies they may have called home for years, but they’re also facing the daunting prospect of job hunting while headlines scream about “AI taking over human jobs.” Not long ago, another company I follow - let’s call it Acme  - went through a similar round of layoffs. Two employees in particular (we’ll call them Jim and John) showed how mindset can make all the difference. Jim had been at Acme for over 20 years. He was reliable, steady, and well-liked, but not exactly the standout type. When he was laid off, he decided to take some time off before even thinking about his next move. After all, he had a severance package. Didn’t he deserve a break after two decades of hard work? John’s story was different. Though he hadn’t been at Acme as long, he’d built a strong reputation and had both technical and leadership skills. Instead of...

Finding Clarity in the Chaos of a Job Search

Job searches are humbling. They test your confidence, your patience, and your ability to stay motivated when things don’t move as quickly as you’d like. But they also teach you things about yourself that you might not have learned any other way. For me, the past few months have been a crash course in rediscovering what really matters: not just in a résumé, but in relationships, self-perception, and how we use technology to help tell our stories. Here are three lessons that stood out. Reach Out to Your Network (Long Before You Need It) Your network is a living thing. It requires upkeep, time, and attention, just like a flower garden. You can’t ignore it for years and expect it to bloom the moment you need it. Start planting early. Stay in touch with people whose paths you’ve crossed - colleagues, mentors, partners, even those you only worked with briefly. Drop a note once in a while. Comment on their posts. Share something that made you think of them. These small gestures are the sunl...

So What is this IPaaS Stuff, Anyway?

 In my last post , I discussed how no-code/low-code platforms fulfill rapid development of business applications - addressing the needs of the Citizen Developer (a Gartner term  first used around 2009).  I also commented on how this specific objective limits their ability to provide true integration capabilities, which require the flexibility to adapt to the myriad variations of infrastructure.  This is a concern because companies often have acquired legacy systems via M&A activity while simultaneously investing in new technology solutions, resulting in a mishmash of systems with multiple ways of accessing them. In this post, I'd like to examine how the needs of the latter group are met by describing some key capabilities that are "must-haves" for any company looking to execute on a digital transformation strategy.  In order to do this, let's define who the target user base is for such a technology platform. Disclaimer:   I work for MuleSoft (a division...