“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.
\\ JMM
Next Generation Technology Leadership, Starting With People
“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.
\\ JMM
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.
\\ JMM
Must Read: http://www.catb.org/~esr/faqs/smart-questions.html
\\ JMM
From: http://www.dslreports.com/forum/r29293609-How-Does-WHT-Do-It
“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.
\\ JMM
“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.”
– Steve Moore, Director, IT Operations, Santander Consumer USA (2017)
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.
\\ JMM