atrophy…

and what do you do about it… if you were like me, you did route or switch first for ccnp, then finished with tshoot… i did switch first, doesn’t matter… the fact is i spent 5-6 months on switch, then 5-6 months on route, then about 3 months on tshoot… some people might think that’s slow although i do not… like i always say, there is no rush…

and here is how i went about it although i do not recommend this approach… for the 5-6 months of switch, that’s all i did… likewise for route for 5-6 months, and then the 2-3 months of tshoot…  i immersed myself each time in each category… i took my time with tshoot unlike most because i enjoyed the consolidation… i read too often about people racing through tshoot and i wasn’t going to be that guy… i did wallace’s ocg, his videos, the net acad lab manual, built the cisco topo and had a great time with boson’s tshoot sim trainer, etc.

which leads to the point: atrophy, and the fight against it…

atrophy happens… it is unavoidable…

so what am i doing about it? like the theme of this place, i begin again but adjust the tools…

the first 500 pages of wendell’s ccie ocg is review, and that is good… i’ve been through the ccie quick review and that is mostly review except for qos, mpls and multicast… those last three i’m spreading out… i will pick them up as i go along in a constant state of deep dive review… in other words, no more immersion to exclusion…  which means anki’s, constant testing, back to doyle, going forward a little, then back again, then back farther, and always core rejuvenation, l2-3, igp’s and bgp, osi and rfc’s…

no more segmentation… my plan is to see this thing as a whole… i think a little bit of everything over time is better than a lot of one thing…