Does Network Cabling Matter ?

Cabling is important. Its need to be good enough. The problem I have with cabling is that people spend way to much time fussing, fretting and fooling themselves that having nice cabling actually has value.

You should be spending time in meetings, writing scripts or buffing up your excel skills to work out the software subscription licensing costs.

Q. Want your advice on a cabling colour scheme for our new data centre ?
A. I DO NOT CARE. IT JUST HAS TO WORK. NO REALLY. I JUST DONT CARE

From Blog Ethermind, June 2018

I read Greg Ferro. I have read his blog for many years. I feel his pain and acknowledge it.  And, although this argument is well written, it is worthy of comment for those who choose to think different.

You see, I do fall in the camp that cabling is important. It’s representative of many things that exist in Information Technology that are under the covers.  Cabling determines how serious you are, how disciplined your IT show is, and the attention to detail your team has.  Yes, cabling says all that.  And when you invite me over to see your data center, it’s what I am thinking when you show off your hard work.

“Network cabling usually only represents 10% of the total technology spend.” – Bill Atkins, during his time at Panduit

Yet, we run the production IT show on that cabling.

“Sometimes you have to do IT two or three times to get it right.” – Former CTO (Name Witheld)

Ouch.  Doing the same things two or three times is not cost efficient and often indicative of culture.  Did you hire the right people and put them in the right seats?  Did we listen to our wiring experts or follow the misguided advice of “this is how we’ve done it for 20 years”?  Two or three times in the wire business is great for the manufacturer and installer, bad for the organization writing the check.

Why Cabling Should Be Important To IT People

I didn’t say critical.  But there should be a standard to hit, as IT craftsmen.  A guide to follow.  Here is my top 5 things I recommend peers to consider when cabling.

#1.  Wiring should be easy to understand.  Color codes and design.  BICSI.  ANSI/TIA/EIA-606-A, Administration Standard for the Telecommunications Infrastructure of Commercial Buildings, or the updated ANSI/TIA/EIA-606-B documents these standards.

#2.  Wiring should be easy to troubleshoot.  As-Builts in all data centers and cable plants.  Consistent labeling throughout the facility.  Velcro over zip-ties.  Basket tray versus cable tray.  Combined wire with slack vs. just letting it hang.

#3.  Quality versus Crap.  Mid-grade wire versus minimally compliant.  Wire for the 20 year plan vs. no plan.  1GB is often plenty.  10GB is overkill if your back end can’t support it.  Think hard about plenum vs. non-plenum.

#4.  Manufacturer and installer proud.  When the manufacturer wants to show your work to their prospects, that’s a good sign they’ve done it right.  Choose certified installers.  Ask the question.  Then choose quality products that align with your team’s standards.

#5.  Wire once.  Your ROI is far better achieved when the installer comes out to do the big job versus coming out multiple times over 2-3 years.  Multiple times often equates to two times the labor cost.  Your not saving money and the chances of mistakes are actually higher.  Wire once, if at all possible.  And then ask the manufacturer to QA your job during your walk through.

\\ JMM

Why You Are Being Asked To Be in CAB

Today’s blog is from the mailbag of notables.  The context of this email is when I was “leading by walking around” and overhearing a few employes not wanting to go to CAB.  Not wanting is putting it nicely.  CAB is “Change Approval Board”, which is mostly a call to talk about the changes happening to the production environment.

From: Jonathan Merrill
Sent: From My Desk
Subject: Why You Are Being Asked To Be in CAB
Importance: High

Just overheard “Why do I need to be at CAB. I don’t have changes”. Not the first time this has been said. And it’s not unnoticed those team members who don’t show up. Before you say, “busy”, I know everyone is busy. We are all busy. Nevertheless, here is why I encourage you to be at CAB every time:

1. If you do have a change, you need to explain to CAB what the change is, what it will impact, and allow architects and SMEs to chime in. We’ve had one over-ride since we started CAB, which saved us from an embarrassing situation.

2. You listen in on what’s changing in our environment. Operations teams must have the pulse on what’s going on. If you don’t know, how can you react? Putting things together is a skill, just like listening and comprehending. All three should be applied in CAB.

3. Opportunities to sharpen your saw putting in changes. Once we get some consistent muscle memory on non-standard changes, let’s talk about standard changes. Until then, let’s learn from each other and ensure we understand the why about change management. I’ll need your help to train other teams once they get incorporated into our change system.

If you’re working on a critical ticket, production outage in flight, or anything affecting a client ability to process, then your at least armed with what changed.

If your actively engaged in a production issue, clear it with your manager and let him or another team member represent your change in CAB.

Any other reason… eh, no. Knowledge culture, folks. Root word is “Know”. We need you to know. I need you to know. This is the culture we are building. Please participate. Everyone…

\\ JMM

When A Leader Told Me To Stop Reading Books…

“Jonathan, you need to stop reading books.  They are hurting your career.  Read the email I just sent you.” – Name Withheld (Obviously)

I would bet in any career field, you run across people who say things that are incredibly damaging in multiple ways.  Causes pause for how toxic or caustic people get into leadership positions.  Nevertheless, the most outrageous comment I’ve ever been told is to stop reading books.

If you know my leadership style, then you know I perpetuate the knowledge culture, which is heavily based on DevOps’ CAMS (Culture, Automation, Measuring, and Sharing).  Working with other teams who don’t embrace that philosophy can and does create friction.  Which is where education is applied.  Culture is critical, we all agree.

So, if your wondering what the email said, I’ve kept it in my personal journal.  Sharing it’s entirety to you editing out business bits:

From: Director, Information Technology
Sent: Long Long Time Ago…
To: Jonathan Merrill
Subject: Communication

I wanted to tell you something I learned a long time ago.  What you did yesterday or last week or last year is almost worthless.  I too have won [people] awards.  They mean nothing.  The business world is focused on what have you done for me now.   The growth of teams is far more important than most anything else.

One of the main things that I desire is that I would rather make progress than simply prove that I am right.   As long as the progress is in the best general direction then it will likely make things better.  In time possibly it will convince people (that aren’t under me) that it was a good idea.  Maybe it shows how it wasn’t.  But I don’t try to emulate anyone.

The people you list (Leonici, Maxwell, Wooten) are mostly wrong in any approach they suggest.  Each approach has to be custom tailored for the situation.  I find that most of the books people write all say basically the same thing.  Many of them are worthless and if they are good I take only a few points from each of them that I have found worked.

For example I remember when everyone said emulate Jack Welch and his leadership style.  I started reading about him and it sounded impressive.  Then I started learning that it wasn’t uncommon for the company to lay off people all the time just to improve stock price.  I found that his words lacked practice.  So he said the right things but practiced a form of management that basically resulted in turn over at all levels (forced or not forced).  In time I figured out that in my opinion he was just another useless manager who had some good ideas but his ideas likely only worked one time in one situation and me saying I would use them was highly suspect.

So really I hate to say it (good or bad) but I don’t study anyone.  I keep a list of things I have learned and try to put who taught it to me.  Outside of that I don’t worry about it.  Graduate school taught me that for the most part.  Good management is 50% how you treat people and how they perceive you and 50% of your ability to define what you want.  Combine those and you likely get progress.

Sounds seat of the pants I know but how I work.

Let’s dig into a few of these statements, as parts of his email is peppered with logic, and where it goes off road.

#1.  What you did yesterday or last week or last year is almost worthless

Leaders are always judged positively by their achievements.  Finding the achievement pattern leads to good hires.  Not tracking your achievements nor having a track record of your achievements is a professional miss in self-development.  I argue all people, from help desk to VP, IT should actively track achievements.  Marry them up with your personal and professional goals.  Minimally, present them annually during the evaluation process so the organization understands what your about and the value you bring.

#2.  As for selling on approaches or styles I rarely if ever do that.  Nor will I start.

Managing a team on democracy and goals is good, but if the culture isn’t set to create the operating context of expectations, then that team is no different than a mob.  People want great cultures.  People desire to know the boundaries so they can freely do their job.  I would argue effective leaders have a style and actively sell/mentor approaches to their people.  Ineffective leaders do not try.

#3.  The people you list (Leonici, Maxell, Wooten) are mostly wrong in any approach they suggest.  Each approach has to be custom tailored for the situation.

How can you argue with the results of those leaders who study and embrace good leadership principles versus those that do not?  We take what is learned and apply it to any situation.  Most situations require customization as no one things fits.  I argue studying principles of success does far better to educate versus only depending on your last leadership experience.

#4.  I remember when everyone said emulate Jack Welch and his leadership style… I found that his words lacked practice.

I too have read Jack Welch and found many things that didn’t align with my leadership philosophy or brand.  I don’t advertise leading this way, but learning how he led isn’t less important.  We should not read any book and apply it to our life prima facie.  Books should educate us, challenge our thinking, and give us opportunity to change us, make us better, or just entertain us.  I argue practicality alone shouldn’t be a reason to not read books about leadership.

#5.  I don’t study anyone.  I keep a list of things I have learned and try to put [into practice] who taught it to me.  Outside of that I don’t worry about it.  Graduate school taught me that for the most part.

I would argue that going to college should just be the beginning of your life long learning journey.  Not the end.

#6.  Good management is 50% how you treat people and how they perceive you and 50% of your ability to define what you want.  Combine those and you likely get progress. 

Of everything said here, this statement rings most true.  And worthy of underscoring as working with this leader for over a year, I can say he wasn’t intentionally “toxic”.  He was a grounded guy, with a family, bills, car, and problems just like us all.

However, looking back on what he got accomplished during his time, he achieved very little.  Not many strategic things got done.  He touched no one.  Influenced little.  And was quickly forgotten as he left.  Does anyone enter a leadership gig with the desire to leave no legacy?  I would argue no.

I ran across this comic today and it reminded me of that leader and his email.

Source: Jake Likes Onions

If anyone knows the author of this book, please let me know.

\\ JMM