“Attitude, Not Aptitude, Determines Altitude” – Zig Ziglar
Sitting at a recent IT event the commentary turned to forecasting IT’s future. The speaker gave an innocuous prediction about how automation is replacing the average IT worker. The industry has decided and is transforming with terms like DevOps, software defined networking, and emphasis on scripting leveraging Microsoft PowerShell, Ansible, or the liking.
Later that evening, the family and I caught Jurassic Park on television. The story of scientists creating a theme park with genetically resurrected dinosaurs from DNA located in petrified tree sap. The movie is amazing, still. Interestingly, I found myself watching and comparing the movie’s themes and messages with the morning’s event.
IT Industry Visionaries Say… The future is Custom Automation.
Dr. Ellie Sattler: So, what are you thinking?
Dr. Alan Grant: We’re out of a job.
Dr. Ian Malcolm: Don’t you mean extinct?
The Cost Of Custom And Automation Dependence: It’s Not Cheap
John Hammond: Dennis, our lives are in your hands and you have butterfingers?
Dennis Nedry: [laughs] I am totally unappreciated in my time. You can run this whole park from this room with minimal staff for up to 3 days. You think that kind of automation is easy? Or cheap? You know anybody who can network 8 connection machines and debug 2 million lines of code for what I bid for this job? Because if he can I’d like to see him try.
Deploying Custom IT Using Automation Is A Journey
John Hammond: All major theme parks have delays. When they opened Disneyland in 1956, nothing worked!
Dr. Ian Malcolm: Yeah, but, John, if The Pirates of the Caribbean breaks down, the pirates don’t eat the tourists.
IT Developers Argue Automation Reasons For Operational Greatness
John Hammond: I don’t think you’re giving us our due credit. Our scientists have done things which nobody’s ever done before…
Dr. Ian Malcolm: Yeah, yeah, but your scientists were so preoccupied with whether or not they could that they didn’t stop to think if they should.
The Fallout Of Automation Dependence: It’s Never Flawless
Dr. Ellie Sattler: But you can’t think your way through this, John. You have to feel it.
John Hammond: You’re right. You’re absolutely right. Hiring Nedry was a mistake, that’s obvious. We’re over-dependent on automation. I can see that now. Now, the next time, everything is correctible…
Dr. Ellie Sattler: John…
John Hammond: Creation is an act of sheer will. Next time it’ll be flawless.
Realizing IT Automation Dependence Isn’t A Viable Reality.
Dr. Alan Grant: Hammond, after careful consideration, I’ve decided, not to endorse your park.
John Hammond: So have I.
This was meant to be a humorous take on a serious topic that is affecting the IT industry in big ways. Long time IT architects and engineers recognize there may be simple truths here, but the fight to automate everything continues to rage on. Granted, many shops have seen irrefutable gains in this space. Look deeply inside those cultures and those leaders. I suspect you’ll find the extraordinary, the exceptional, outspoken, the fighter, and maybe even crazy.
I like to play in those spaces too, but sitting at DevOps, Cisco, and other user groups around DFW, the constant theme I see and hear, many with frustration in their voices, is the desire and want is there but the capability, knowledge, culture, and leadership is not. Creation is an act of sheer will. But, the definition of insanity is creation and sheer will gone asunder.
“Do you know why we wear ties? To signify seriousness of purpose.” – Bobby Axelrod, Billons, Episode 12
Love this quote. So many things can be said about it.
Please keep in mind that the key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC 2119.
One of my peers cited this in one of our project meetings. Nebulous or poorly interpretive descriptions of technical requirements should be avoided.
“Well engineered projects are indistinguishable from crazy ideas.”
I resonated with this statement as we spoke of the important of wiring standards, craftmanship, and the sad state of installations in so many IT shops. Why are well engineered projects, like data center wiring, met with so much resistance? Answer: cost, time, and effort are not always well articulated nor understood by the masses. And often, trump all unless you spend the time showing amazing value for that effort.
A wire is not always a wire. Kudos for those shops that get it and embrace good IT. It’s crazy, I know.
“While I understand the process and how it should work, there is a chance that someone could go in and make changes [to servers]. We have to think like a Risk Manager and the possibilities that could happen.” – Today’s IT Leader
Just recently, we had several conversations where system engineers lamented on the amount of work risk mitigation has created. While this often is viewed through various colors of lenses and often tempered with bias, the point was not to just express exasperation about the volume of reactive work.
The point was to proactively think like a risk manager and head things off so it’s built into the DNA of the technology. Are we really thinking this way? Are we creatively thinking about risk as we architect solutions.
Let’s prevent the backlog versus react to it.
“It’s Official, 2017 has been coined “The Year of KNOWLEDGE”. Many, if not all of you, have started, or plan to start your Knowledge Management Initiative this coming year.” – Josh Addington
It’s probably no surprise that managing our proprietary and intellectual knowledge for commodity services, such as technical support, is still a problem in 2017. Interestingly, people are doing something about it through community initiatives. This is one such here in Dallas, Texas.
Excited to see what fruit this will bear, what ideas can be shared, and if we must, collectively display our sorrow at the state of our own challenges in this tough space.
“My feedback is the lack of intuitiveness drives complexity.”
– J. Merrill
The context of this quote covers so many different areas, in my career. Everything from user interface and workflow discussions to policy and procedure brainstorming. It’s very easy to run simple into the ditch.
Simplicity can only be accomplished with the addition of intentional and intuitive interfaces in writing, electronic, and in practice.