Converging On The Edge

ACL: 17 Steps to Correcting a Misconfiguration

Read with caution. The procedure below is highly tuned and known to cause huge pay raises and new big important titles - use with care.

Remain calm.
Tweet about it.
Watch your Twitter stream for a minimum of five minutes anxiously waiting for all your followers to sympathize.
Read the latest Dilbert to gain mental clarity.
Run and tell your boss. Make sure to be as clear as possible ~~that it wasn’t your fault~~ to communicate the *right* way to configure it.
Blame as many people as possible and laugh about it with your boss. This is a good time to show your awesomeness. (Your review is coming up after all – gotta look out for number one!)
Go back to your desk.
Huff and puff as loud as you can, talk under your breathe and make sure people notice how distraught you are.
Next, talk to at least one other employee about how unbelievably stupid the configuration is.
Write a script that corrects the misconfiguration.
Submit it to change control and plan to talk about it in tomorrows change control meeting.
Make the change – yes, now, change control is for losers, you’re above peer review. Besides no one will find out you did it before the change control meeting.
Whoops, network is down – act like you don’t know what it is.
Pretend to troubleshoot the issue for at least forty-five minutes.
Re-run your script with ‘no’ in-front of all the configurations.
*Graciously* accept the praise and accolades for fixing the issue .
Go home with your head high – you did a fantastic job! (If only all engineers were as thoughtful and brilliant as you).