349 Words. Plan about 1 minute(s) to read this.
First day at CCDE bootcamp with Jeremy Filliben. Thoughts:
(1) Jeremy has given a lot of thought to content, both to *what* content will be covered, and *in what order* the content will be covered.
(2) There’s a lot of material here. When it gets into the technical lecture, there’s an assumption you already have a clue. I’m holding my own so far, going through mostly IPv6 and OSPF in today’s technical lecture sections. But if the material had been new or relatively unfamiliar, this is not the context in which you’d be learning the details. The point being – Jeremy is hitting all the key points that you need to grasp so that you can intelligently apply technologies to business cases. But this isn’t about holding your hand through every little nuance. There just isn’t that kind of time. My opinion is that the coverage is exactly right for where you’re supposed to be in your career if you’re attempting the CCDE. You’ve been around the block. This ain’t your first rodeo. You know where your towel is. And you can Google the what you don’t know. I did a bit of that tonight, adding some docs to my Evernote.
(3) There’s homework. Every night, we’re being sent home with case studies, which will form the foundation of the next morning’s discussion. The first one I just completed, and it took me something over an hour. I didn’t time it that closely. The idea of the case study is to emulate the sort of scenario you might see on the practical exam, so I’m very much looking forward to the post-mortem in the morning.
(4) As with the CCIE lab, the CCDE practical exam demands a certain approach. Jeremy has provided a lot of insight into that. How to think. How to interpret questions. A methodology to follow. Etc. I feel like my mind is better organized, now that I have a better grasp on just how the practical is laid out, and what the intentions are of the exam designers.
I’ll write more over the next few days, synaptic powers permitting.
Ethan Banks writes & podcasts about IT, new media, and personal tech.
about | subscribe | @ecbanks