When you run the script, run ALL of the script...

Started by deanwebb, November 28, 2016, 04:23:42 PM

Previous topic - Next topic

deanwebb

Dealing with outsourcers...  :developers:

When I give you guys a script to run on a bunch of switches, run ALL of the script, not just the parts that you think are cool. Now we have to go back and figure out the parts you failed to run so that we can submit another work order to tell you to get that stuff into the running config.

Oh yes, and don't forget to write mem. Sometimes, switches reboot. We still need these changes on the config if the switch reboots.

That is all. I'd like to be alone, now, in my misery...

:facepalm1:
Take a baseball bat and trash all the routers, shout out "IT'S A NETWORK PROBLEM NOW, SUCKERS!" and then peel out of the parking lot in your Ferrari.
"The world could perish if people only worked on things that were easy to handle." -- Vladimir Savchenko
Вопросы есть? Вопросов нет! | BCEB: Belkin Certified Expert Baffler | "Plan B is Plan A with an element of panic." -- John Clarke
Accounting is architecture, remember that!
Air gaps are high-latency Internet connections.

wintermute000

if outsourced is true:
   try:
       do(task)
   except Exception as e:
       print(tell_them_exactly_what_to_do_or_else_they_won't_do_a_goddarned_thing)




icecream-guy

You really need to provide them with a checklist.
:professorcat:

My Moral Fibers have been cut.

that1guy15

This reminds me of newer linux admins trying to get a server setup. Who cares about the 30 errors that flew past on the screen or the dependency issues for that package. Just keep moving and surely it will work.

But then again, Ive been guilty of this myself...
That1guy15
@that1guy_15
blog.movingonesandzeros.net

deanwebb

Above mess is with a checklist and saying exactly what to do. That's how we can hold them responsible for the work.
Take a baseball bat and trash all the routers, shout out "IT'S A NETWORK PROBLEM NOW, SUCKERS!" and then peel out of the parking lot in your Ferrari.
"The world could perish if people only worked on things that were easy to handle." -- Vladimir Savchenko
Вопросы есть? Вопросов нет! | BCEB: Belkin Certified Expert Baffler | "Plan B is Plan A with an element of panic." -- John Clarke
Accounting is architecture, remember that!
Air gaps are high-latency Internet connections.

Otanx

This is why I started requesting they log their session when doing work. Then when they screw it up I can see what they screwed up.

-Otanx

icecream-guy

#6
I do that myself to CMA (CYA) all my terminal session windows are logged on a daily basis just so I have proof,  stuff has happened in th e past where fingers were pointed and I had not proof that is wasn't me. now I do.   I also edited my .bashrc   and changed my prompt to
'\d \t [\u@\h \W]\$ ' so the date and time are logged on every <cr>. have have yet to change the device prompts to include date and time.
I've come close to losing track of my timings (when things happen) when logged into a device for long periods of time. but found the start time and end times sufficient to CMA.


On the checklist thing, a co-worker recommend for me to read Checklist Manifest by Atul Gawande. I'm about 1/2 way through, interesting read about how checklists have changed the world, but I'll not be reading books by other general surgeons.  He like to tell stories and some are quite in detail.
:professorcat:

My Moral Fibers have been cut.