Best viewed at 1.5 speed at least.
Odd that when they started, it seemed they had used 10 foot long cables to span 1 foot distances on every connection.
That's going to be so much nicer for them to work with now. Good work guys.

That probably took the better part of a week...or more..

"It's too long, but it's impressive."

That's.

What.

She.

Said.

" Now I have to go clean off my desk."

damn that is A LOT of uselessly long cabling at the start!

Unfortunately, not uncommon in the slightest. I've done two jobs like this (at a previous employer and at my current job when we tore down the server room to install proper heat tunnels as our 1990's vintage air con wasn't keeping our server room under 35 deg cel).

People don't fix lazy patches (and it's not really advisable to pull cables during production because wackiness ensues), so eventually you end up with an awful mess. When someone does decide to clean it up, you have so many systems (and associated downtime) that management baulks at committing, reasoning that "if it's working, don't fuck with it". Then you reach the inevitable disaster point where you lose a vital system and cannot fix it because you lost a cable in the mess.

Longer patches get used to go around the monstrous mess created and eventually get buried as more and more are added, or repatching is done. Or it's the only cable they had on hand. Or they can't be bothered getting a more sensibly sized patch. ; )

It also looks like they were fixing up the fibre channel patches at the same time.

@ CharlieM, 3 days according to the white time stamp in the top left corner ; ).

"Hey, uh, someone set downtime in Nagios, right?"

#CablePorn

natty dread

Which is what she said, later...