Aug
30
Route-map Names
Filed Under CCIE General
You know how all the camps, cods, etc, etc talk about using route map names that you can easily indentify? I always seem to name mine out of anger, frustration, or just joy for the task that I am currently working on.
For example:
ISUKATTHIS
WHYAMIDOINGTHIS
WHYDOIWORKINIT
IHATECCIEPURSUIT
OMGTHISLABSUCKS
PLEASEENDTHISTORTURE
WHYDIDIGETMARRIED
MANINEEDTOSHOWER
WHATISFORDINNER
DIDITAKEOUTTHEGARBAGE
BABIESRPOOPFACTORIES
JUNIPERROCKSTHEHOUSE
Maybe if I use some of these on the lab the proctors would get a kick out of it…
Comments
6 Responses to “Route-map Names”
Leave a Reply
LOL! Funny man! I don´t usually do the same, but sometimes I feel like it!
Cheers,
Caue Wailemann
LOL!!! “IDARETHISPROCTORTOFAILME” is actually an IOS cheat code that will guarantee you passing grade on the lab. Or is it unlimited lab attempts? I can’t remember but you should definitely use it in the real lab.
LOL that and the Juniper one should help out my score. God help them if they interview me as well
“…any questions for us? Yes why is your stock sucking it up lately? Fix that shit will you!”
Nice Carl…I always found funny variable names to be a good way to find some humor in this sort of thing.
My buddy and I always used the variable “pants” for damn near anything…it makes such a great variable in so many ways.
pants.zip — unzip pants
In UNIX you could tar pants
IOS — enable secret pants
UNIX – touch pants, rm pants
Perl – require pants, open pants, split pants, flush pants…
C Programming – Switch pants, free pants
SQL – Select pants, insert into pants, drop pants
Remember kids, when you choose a good variable name, the fun never ends!
I miss rm * -rf
[...] feel sorry for the poor switch but my memories are filled with images of that photo shoot that CCIE Journey did for goatse.cx which are far more horrible than test patterns. Posted by cciepursuit [...]