Category Archives: Certification

Repetition Without Repetition

Posted on by
Reply

I just finished spending a wonderful week at Cisco Live EMEA and getting to catch up with some of the best people in the industry. I got to chat with trainers like Orhan Ergun and David Bombal and see how they’re continuing to embrace the need for people in the networking community to gain knowledge and training. It also made me think about a concept I recently heard about that turns out to be a perfect analogy to my training philosophy even though it’s almost 70 years old.

Practice Makes Perfect

Repetition without repetition. The idea seems like a tautology at first. How can I repeat something without repeating it. I’m sure that the people in 1967 that picked up the book by Soviet neurophysiologist Nikolai Aleksandrovitsch Bernstein were just as confused. Why should you do things over and over again if not to get good at performing the task or learning the skill?

The key in this research from Bernstein lay in how the practice happens. In this particular case he looked at blacksmiths to see how they used hammers to strike the pieces they were working on. The most accurate of his test subjects didn’t just perform the same movements over and over again. Instead, they had some variability in their skill that allowed them to be more accurate or efficient over time. They weren’t just going through the motions, as it were. They were adapting their motions to the need at the moment. This allowed them to adjust their aim if the piece had moved or needed a lighter touch in an area that was thinned too quickly.

Bernstein said this about the way that the blacksmiths practiced their art:

“The process of practice towards the achievement of new motor habits essentially consists in the gradual success of a search for optimal motor solutions to the appropriate problems. Because of this, practice, when properly undertaken, does not consist in repeating the means of solution of a motor problem time after time, but in the process of solving this problem again and again by techniques which we changed and perfected from repetition to repetition. It is already apparent here that, in many cases, ‘practice is a particular type of repetition without repetition’…”

The quote above illustrates a big shift in thinking for people who play sports or perform some kind of task. Instead of merely repeating the movements over and over again until perfection (the ‘means of the solution’) you should instead focus on solving the problem over and over again and adapting your skill to that end. It sounds silly and somewhat pedantic, but the key is in the shift of thinking. For basketball players, it’s not about perfecting your spin move to get around a defender. It’s about understanding the need to get around the defender and how best to accomplish that for different kinds of people defending you.

Avoiding Autopilot

Most of the content you’ll see around the concept of repetition without repetition is for sports players practicing skills. However, I think the concept extends perfectly to the IT certification space and troubleshooting skillset as well. There are a number of important things that we need to learn in order to do our jobs or earn a specialization but we need to remember that the goal is to solve problems and show mastery, not to memorize commands and perform them like a simple batch file.

Here’s a perfect example that I’m very guilty of doing. When you log into a Cisco router to do something, what do you normally do first when you get to the CLI prompt? You almost always need to be in privileged EXEC mode, right? That’s the enable command. When we want to configure something on the router we usually have to be in the router configuration mode, which is the configure terminal command. So far, so good, right? Most of you have already picked up on the fact that you can shorten those commands to save time typing out the whole name, which is an important skill to have when you’re configuring a series of devices or trying to do it in a short timeframe. So enable, configure terminal instead becomes en, conf t. It’s like muscle memory at this point.

How many times have you logged into router to check the routing table and accidentally typed in en, conf t from muscle memory only to remember that the routing table has to be displayed from EXEC mode, not configuration mode? You chide yourself for typing in conf t and back out to look at the table. But what you’ve really done is shown the power and drawbacks of repetition. If you spend hours upon hours typing in the same commands over and over again you will type them in the same way every time. So much so, in fact, that you forget that you’re doing it until you realize you put something in that you shouldn’t. You knew when you logged in that you wanted to display the routing table. You knew that was available in EXEC mode. And yet your brain and fingers automatically typed the same commends you always type when you log into the router.

The idea of repetition without repetition says that we need to consider the how of solving a problem and the skills needed above and beyond the simple skills themselves. Sure, there may only be one or two commands the achieve a desired output or effect but we should know how the both impact the performance of the device or how they can impact the outcome of a situation. This is especially important for exams that like to restrict your ability to use specific commands or are written to direct you in a specific line of thinking. Anyone who has ever taken the CCIE lab exam knows how this works. They restrict you from using common commands or give you a question with two possible answers only to limit that to one with a later requirement. The test asks you to configure something in an earlier section and then gives you a task that can undo that configuration if you’re not aware of how it interacts with everything else. If you’ve ever created a routing redistribution loop on accident you know what that feels like.

The Indictment of AI

In a way, repetition without repetition is the key of what makes a person an apt problem solver. By approaching problems with a mindset and not just a skillset you open your world to new possibilities and considerations. You know there is more than one way to skin a cat, as the old saying goes. You’re smarter than an artificial intelligence, which only works within a set of bounds with skills and apparent intelligence that repeats what it’s told or uses a very narrow focus every time to provide consistent results.

Computer programs and algorithms are dumb because they will solve the problem the same way each time they are executed. People will solve the problem and then start analyzing the results to find new, better, and faster ways to implement solutions. That’s the heart of learning. It’s not just performing the subtasks of the skill to perfection every time. It’s about learning how to implement them in a better way each time and arrive at better solutions to problems with the variables are changed. It’s why the human mind that has been adapted for centuries and millennia to look for patterns can be tricked into adapting those patterns to new concepts and made to “grow up” by learning over time to adjust to new inputs or fresh data. That, more than anything, is why repetition without repetition makes us better than the AI we’re programming to eclipse us.

Tom’s Take

When I first heard of this concept I thought it was some new idea from sports science that was borne from modern research techniques. I was shocked to learn it was discovered before I was born and has roots in some of the oldest trades we can think of. What it proves is that the human mind and body are very wonderful things that react perfectly when challenged in the right way. The brain will adapt and overcome when presented with new inputs. The way we grow and improve ourselves is not wrote memorization or continuous skill repetition. Instead, if we internalize the importance of the outcome over the means of getting there we will find ourselves smarter and more able to be flexible when new challenges come our way.

Overcoming the Wall

Posted on by
Reply

I was watching a Youtube video this week that had a great quote. The creator was talking about sanding a woodworking project and said something about how much it needed to be sanded.

Whenever you think you’re done, that’s when you’ve just started.

That statement really resonated with me. I’ve found that it’s far too easy to think you’re finished with something right about the time you really need to hunker down and put in extra effort. In running they call it “hitting the wall” and it usually marks the point when your body is out of energy. There’s often another wall you hit mentally before you get there, though, and that’s the one that needs to be overcome with some tenacity.

The Looming Rise

If your brain is like mine you don’t like belaboring something. The mind craves completion and resolution. Once you’ve solved a problem it’s done and finished. No need to continue on with it once you’ve reached a point where it’s good enough. Time to move on to something else that’s new and exciting and a source of dopamine.

However, that feeling of being done with something early on is often a false sense of completion. I learned that the hard way when I was studying for my CCIE. Every question has an answer. Some questions have a couple of different answers. However, knowing the correct answer isn’t the same as knowing all the incorrect answers. Why would I want to take the time to learn all the wrong things instead of just learning what’s right and moving on to the next topic?

The reason to keep going even after you know what’s right is to recognize what the wrong thing looks like. When studying you’re often confronted with suboptimal situations or, especially with the CCIE, put into positions where you can make mistakes that will lead to disaster if you don’t recognize the pitfalls early. Maybe it’s creating a routing loop. It could be a choice between two methods of configuration that really only has one correct answer if you know why the other one will cause problems.

Persevering through that mental wall that says “you’ve done enough” is important because the extra value you gain when you do is critical to understand the myriad ways that something can be broken. It’s not enough to know it’s not right. You have to recognize what isn’t right about it. That kind of understanding can come from practice experience, like making the mistake, or through careful study in controlled situations like learning all the wrong ways to work the problem.

The Challenging Ascent

Getting over that wall isn’t easy. Your brain doesn’t want to struggle past the right way to do things. It craves challenge and novelty. You’re going to have to work against your better nature to get to a point where you’re past the wall. Don’t be afraid to lie to yourself to get where you need to be.

When running I will trick myself when I hit my mental wall by saying “one more song” or “one more block” when I’m ready to give up. The idea that I can make it a short distance or short amount of time is comforting to my brain when it wants to stop. And by tricking it I can often push a little harder to another song or two more blocks before I get completely over the wall and have the mental toughness to continue.

Likewise, when you’re studying and you’ve found the correct answer you need to push yourself to find one incorrect way at first. Maybe a second. If it’s something that has configurable settings you should investigate a few wrong values to figure out what happens when things are outside of bounds or when they’re just a little bit off. Maybe convince yourself to figure out two or three and write down the results. If one of them ends up being really interesting it could spark you to do more investigation to find out what caused that particular outcome.

You’ll find that you can get past your mental blocks much easier with tricks like that. More importantly, you’ll also find that you can get them to pop up faster and be overcome with less effort as you understand when they happen. If you’ve ever sat down to study something and your brain immediately wants to give up you know that the wall is right in front of you. How you overcome it can mean the difference between truly understanding a topic and just knowing enough about the answer to regurgitate it later.

Tom’s Take

As always, your mileage may vary with skills like these. I’d wager that most people do hit a wall whether it’s running or doing math or studying the intricacies of how OSPF works over non-broadcast networks. Don’t settle for your brain telling you that you’re done. Seek to really put in the work and understand what’s going on. Write everything down so you know what you’ve discovered. And when that wall seems like it’s too high to climb just whisper to yourself you’re going to climb another foot. And then another. And pretty soon you’ll be over and in the clear.

Being the Best at Beginning

Posted on by
Reply

The other day I was listening to an excellent episode of The Art of Network Engineering talking about technical marketing engineers (TME). The discussion was excellent and there was one line from Pete Lumbis in the episode that stuck with me. He said that one of the things that makes you good as a TME is being an “expert beginner”. That phrase resonates at lot with me.

Fresh Eyes on the Problem

I talked a bit about this last year when I talked about being a beginner and how exciting that it was to start over with something. As I compared that post to the AONE episode I realized that what Pete was talking about was a shift in mindset that gives you the energy and focus to pick things up quickly.

You may have heard the phrase “familiarity breeds contempt”. It’s a common phrase used to describe how we feel less impressed with things the more we learn about then. Our brains are wired to enjoy new things. We love new experiences, going to new places, or even meeting new people. The excitement and rush that we get from something unfamiliar causes our brain to devour things. It’s only once we become familiar with them that we feel the contempt set in.

It’s not always possible to avoid the contempt part of things. Think about something as dreary as your morning commute to work, whether it’s walking down the stairs or driving to the office. I used to joke that my car was practically on auto-pilot most mornings because I knew every bump in the road and every turn by heart. When I would go somewhere new I would have to focus more on road signs or directions.

Back to Basics

The beginner aspect of things is easier to deal with. That’s because we can trick ourselves into seeing something with fresh eyes. On a number of occasions I’ve mentioned my friend and mentor John Pross and his assertion that every upgrade or deployment that happened was like the first time doing it. He never took anything for granted. He always took things step-by-step. While this had the affect of him making sure everything was followed to the letter it also gave him the beginner aspect of looking for ways to improve or discovering new solutions to problems along the way.

Once the contempt or apathy sets in you’re going to get very good at just clicking through the steps to get to the end as fast as possible. If you don’t believe me think about how many times you’ve given directions that involve something like “Just click Next, Next, Next, Next and then you’re done”. Trust me, it sounds funnier when you say it out loud. But it speaks to the fact that we know the dialog boxes so well that we know they aren’t important. But what if they are?

If you want to understand what it feels like to be a beginner again and you’re having a hard time getting yourself in that mindset you should find a beginner and coach them through a task like a setup. Don’t just tell them what to do. Let them figure it out. Answer questions as they come up. Make them explain why they’re doing something. I bet you’ll learn a lot more as you have to help them understand why that configuration line is in there or why you always choose twice the amount of RAM in an instance. Once you see the process through the eyes of a beginner you have to learn it more completely in order to help them understand it.

In some roles, like a TME or a VAR engineer, the ability to be an expert beginner is critical to your job. You have to see a technology for the first time and pick up the basics quickly. I used to tell people that the excitement of being an engineer at a VAR was the variety of problems I’d be called on to solve. One day might be wireless clients. The next could be iSCSI storage arrays. Whatever the case may be I could count on finding myself in a new situation pretty regularly. It kept things exciting and made me realize I had to stay on my toes.

For those that work as product managers or on more specialized teams you need to make sure you’re taking time to approach things as a beginner. The “same old, same old” may not actually be the same any more. That kind of contempt and familiarity leads to the phrase “the way we’ve always done it” and doesn’t force you to challenge the process to understand how to improve it. Sometimes you need to step back and remember that you have to see everything for the first time.

Tom’s Take

Beginners shouldn’t feel like they’re a nuisance. In fact they should be celebrated for the energy and focus they bring to a task or project. For roles like a TME it’s important to bring the same kind of energy to new things. You can learn a lot when you allow your brain to soak up knowledge like a fresh sponge. More importantly, the ability to be a beginner helps you refine your knowledge base more and will ensure that you can explain a concept or process to someone with absolute certainty.

The Power of Continuing Education on Certifications

Posted on by
Reply

I’m about six months away from recertifying my CCIE and even though I could just go Emeritus now I’m working on completing some continuing education at the end of the year to push it out another three years. I am once again very thankful that Cisco has this as an option instead of taking a test over and over again as the only option to renew my certifications.

As I embark on another journey to keep myself current in the networking community, I realize that the flexibility that education credits offer is more important that just passing a test or learning a new skill. Employers should also be thrilled that knowledge workers have the ability to work on other skills and be recognized for them. Because there are two different paths that this can lead to.

To Be The Best

One of the things that most professionals recognize with continuing education is that you can leverage your skills to race through things. If you’re already an expert at something like BGP or spanning tree why not take courses to improve the depth of your knowledge? This is part of the reason why there are a number of double CCIEs that have Routing and Switching and Service Provider. The skill sets have a big overlap which makes the additional study to pass the other relatively painless.

Taking pride in practicing the same skill set over and over again is something we traditionally associate with athletes and other skill positions. It is a very valid way of showing everyone that you truly are an expert at your craft. Knowing every nuance of the protocol or understanding it to a degree not possessed by anyone else is a real accomplishment. The value you gain in troubleshooting situations is unmatched. It’s easy to become the authoritative source on something because you’ve literally studied every piece of material on it and you know it inside out.

The downside of this kind of approach is that you naturally gravitate toward being an expert on exactly one or two things. Like a cake baker you are great at making one specific kind of thing. You may have more than enough work to keep you occupied for years but if the market shifts you may find yourself in trouble. The deep learning method works with technology that doesn’t get superseded quickly. IP routing is here to stay but we also said the same thing about traditional telephony and FORTRAN. Those may still exist in some form today and the experts are still needed to make them work but they aren’t nearly as big as they used to be.

Covering the Rest

The opposite of a deep expert is one that has a wide breadth of knowledge. This is the area where I feel a continuous learning program really shines. That’s because access to knowledge outside of your specific discipline can be hard to come by without help. Having a list of approved courses for a CE portal steers you in a good direction to take advantage of these offerings.

I remember telling people that I knew I was starting to gain on my knowledge and certification journey when I stopped finding the books I needed at the local book store. That’s absolutely true for those that are trying to reach the pinnacle of their specific skill set. However, those basic books are great to jump into an area you may not be familiar with.

You may think that you can spend your time studying and practicing and getting expert skill levels in a few key areas but you also need to realize that things can shift. Networking professionals today also need to understand programming and cloud and many other aspects of enterprise IT. It’s not even a case that knowing how to use those things is just easier. Instead it’s a case of requiring knowledge in those areas to understand how they interact so you can build more complete systems. You might be able to work on technology with a specific skill set but you won’t be able to work on anything new if you don’t know how all the parts work together.

You may not like the idea of studying lots of different areas of knowledge and that’s totally fine. But if you don’t at least understand that some knowledge of other areas is needed you’re going to find yourself opting out of many opportunities to work on things that are going to be important later.

Tom’s Take

You can choose to be the deep expert or the designer with breadth. The important thing is that the choice is yours thanks to the foresight of companies that embrace a model of learning over regurgitation. If you want to pick up new skills and get credit for them you can. If you’d prefer to be the best at a given discipline then the world is your oyster. No matter what you have the ability to make a choice that isn’t studying for a test every couple of years that doesn’t expand your knowledge. To me, the real value of a CE program is how it makes us all better.

Intelligence and Wisdom

Posted on by
1

I spent the last week at the Philmont Leadership Challenge in beautiful Cimarron, NM. I had the chance to learn a bit more about servant leadership and work on my outdoor skills a little. I also had some time to reflect on an interesting question posed to me by one of the members of my crew.

He asked me, “You seem wise. How did you get so wise?” This caught me flat-flooted for a moment because I’d never really considered myself to be a very wise person. Experienced perhaps but not wise like Yoda or Gandalf. So I answered him as I thought more about it.

Intelligence is knowing what to do. Wisdom is knowing what not to do.

The more I thought about that quote the more I realized the importance of the distinction.

Basic Botany

There’s another saying that people tweeted back at me when I shared the above quote. It’s used in the context of describing Intelligence and Wisdom for Dungeons and Dragons roleplaying:

Intelligence is knowing that a tomato is a fruit. Wisdom is not putting tomatoes in a fruit salad.

It’s silly and funny but it gets right to the point and is a different version of my other observation. Intelligence is all about the acquisition of knowledge. Think about your certification journey. You spend all your time learning the correct commands for displaying routing tables or how to debug a device and figure out what’s going on. You memorize arguments so you can pass the exam without the use of the question mark.

Intelligence is focused on making sure you have all the knowledge you can ever use. Whether it’s an arcane spell book or Routing TCP/IP Volume 1 you’re working with the kinds of information that you need to ingest in order to get things done. Think of it like a kind of race to amass a fortune in facts.

However, as pointed out above, intelligence is often lacking in the application of that knowledge. Assembling a storehouse full of facts doesn’t do much to help you when it comes to applying that knowledge to produce outcomes. You can be a very intelligent person and still not know what to do with it. You may have heard someone say that a person is “book smart” or is lacking is “common sense”. These are both ways to say that someone is intelligent by maybe not wise.

Applied Science

If intelligence is all about acquisition of knowledge then wisdom is focused on application. Just because you know what commands are used to debug a router doesn’t mean you need to use them all the time. There are apocryphal stories of freshly minted CCIEs walking in to the data center for an ISP and entering debug ip packet detail on the CLI only to watch the switch completely exhaust itself and crash in the middle of the day. The command was correct for what they wanted to accomplish. What was missing was the applied knowledge that a busy switch wouldn’t be able to handle the additional processing load of that much data being streamed to the console.

Wisdom isn’t gained from reading a book. It’s gained from applying knowledge to situations. No application of that knowledge is going to be perfect every time. You’re going to make mistakes. You’re going to do things that cause problems. You’re going to need to fix mistakes and learn as you go. Along the way you’re going to find a lot of things that don’t work for a given situation. That’s where wisdom is gained. You’re not failing. You’re learning what doesn’t work so you don’t apply it incorrectly.

A perfect example of this came just a couple of days ago. The power in my office was out which meant the Internet was down for everyone. A major crisis for sure! I knew I needed to figure out what was going on so I started the troubleshooting process. I knew how electricity worked and what needed to be checked. Along the way I kept working and trying to figure out where the problem was. The wisdom I gained along the way from working with series circuits and receptacles helped me narrow things down to one wall socket that had become worn out and needed to be replaced. More wisdom told me to make sure the power was turned off before I started working on the replacement.

I succeeded not because I knew what to do as much as knowing what not to do when applying the knowledge. I didn’t have to check plugs I knew weren’t working. I knew things could be on different circuits. I knew I didn’t have to mess with working sockets either. All the knowledge of resistance and current would only serve me correctly if I knew where to put it and how to work around the issues I saw in the application of that knowledge.

Not every piece of wisdom comes from unexpected outcomes. It’s often just as important to do something that works and see the result so you can remember it for the next time. The wisdom comes in knowing how to apply that knowledge and why it only works in certain situations. If you’ve every worked with someone that troubleshoots really complex problems with statements like “I tried this crazy thing once and it worked” you know exactly how this can be done.

Tom’s Take

Intelligence has always been my strong point. I read a lot and retain knowledge. I’m at home when I’m recalling trivia or absorbing new facts. However I’ve always worried that I wasn’t very wise. I make simple mistakes and often forget how to use the information I have on hand. However, when I shared the quote above I finally realized that all those mistakes were just me learning how to apply the knowledge I’d gained over time. Wisdom isn’t a passage in a book. It’s not a fact. It’s about knowing when to use it and when not to use it. It’s about learning in a different way that matters just as much as all the libraries in the world.

Certification Comfort Food

Posted on by
Reply

I’m a big fan of comfort food. Maybe more than I should be. The idea of something simple and tasty just hits the right spot a lot of time, especially when I’m stressed or don’t have time to do something more involved. I know I really need to be better about cooking but you can’t beat a quick meal that uses something simple and gets the job done, right?

Now, before you ask yourself what I’m on about this week, I want you to think about that analogy in terms of certifications and learning. When we’re starting out in the industry or we’re learning a new skill we have to pick up basic ideas. The more advanced or radical the technology the more we need the kinds of explanations that make the concepts simple to understand. We need the equivalent of learning comfort food. Simple, digestible, and easy to prepare.

Climbing the Ladder

As our skills improve we have the choice to continue on and develop our capabilities to greater depths. Perhaps we want to learn everything there is to know about BGP and policies. We could even parlay that networking knowledge into new adjacencies that build on our skill sets. We also have the option of staying in the basic level and honing those skills. Instead of learning VXLAN we could spend a thousand hours practicing all the ways that you can configure a VLAN.

Which way is right? Is there a need to make a choice? People are going to feel more comfortable doing one thing over the other in almost every case. If you’re like me you want to get to the bottom of every mystery and explore every nuance of something. Once you figure it out you’re going to want to move on to the next hard problem to solve. You become a voracious reader and consumer of knowledge and before you know it you’ve run out of things to consume. It’s partially the reason why I’ve been such a prolific writer for the past twelve years. I’ve been creating the content that I wanted to consume so others can benefit.

The other side of the choice is being content with the skills you have. This is in no way a negative thing. Not everyone that cooks needs to be a four star chef that makes perfect risotto and Beef Wellington every time. There is a place for everyone that learns enough to accomplish their goals and decides that is enough for them. If the above option is the “pull” model where one is trying to pull in new knowledge as fast as possible then this is the “push” version where people must be pushed to learn additional things. Your company might move to cloud and that would facilitate a need to pick up cloud operations skills to complement the ones you have for the network or the virtualization cluster. You’re not actively seeking the knowledge until it’s needed.

Boiling the Mudpuddle

It’s all well and good when you can recognize which type of learner you are. It’s also important to know where your resources are aimed. If your top destinations for content are part of the “push” model and aim at a lower level when you’re someone that wants to grow and investigate new areas you’re going to hit a wall eventually and sour on them.

A personal story for me comes when I was racing through my certification journey in the early part of my career. Once I started with Cisco I was consuming books left and right. Every time I went into the book store I picked up a new tome to teach me more about routing or remote access networks or even firewalls. I would consume that content whenever I could and apply those lessons to my job or my certification process. Eventually I knew I was reaching a limit because there were fewer and fewer books in the bookstore that taught me things I wanted to know. It made me realize there is a target market for these resources.

Things like certification guides are aimed at a wide market. They want to teach skills to the widest possible audience. Not everyone needs to know the ins and outs of EVPN but most everyone in networking needs to know how a switch forwards frames. If you want to sell the most books which would you write about? You’d write the one that covers the most people. It’s a reality of the market. Content for the entry level and the broadest group sells the best. In today’s world the book has been replaced by the blog and the YouTube channel.

As mentioned, I started my blogging career because of the above bookstore issue. Once I started learning things that weren’t in every book I wanted to share those ideas. That got me to Tech Field Day and eventually to different things. It also made me realize that while my content may never have hundreds of thousands of readers for every post it would serve people that needed to find those lessons or understand those topics in a depth that was beyond a paragraph or two in a 400-page encyclopedia of terminology.

To me, the certification comfort food is that entry-level content. It’s always going to be there. It’s simple to write about, especially when you have good analogies to frame new concepts for people. It’s tasty when you’re starving. And you can make a very good living doing it. But if you’re the kind of person that wants to try new tastes and break away from the comfort and ease you’re going to need to figure out your own path. You need to experiment and make mistakes and struggle to conceptualize what you’re talking about. You need to expand your horizons and do new things and then tell the world how you did it. Like a recipe blog or TikTok channel for cooking you’re going to need to put your crazy ideas out there and see how it goes.

Tom’s Take

There are a lot of great creators out there that have made a very good place for themselves teaching newcomers the basics of how things work. I applaud them and wish them nothing but success. I also know that’s not for me. I started writing about my CCIE studies and the challenges I was solving the real world. Now I write about the state of the market or the changing of tech or how to build and lead teams. It’s very representative of my journey as well as the journeys of those in the community that I talk to. My very nature won’t let me stay in a little bubble and create the same things in new ways. I’m going to push the envelope and explore new things. It means I might not land in everyone’s top list but it also means I won’t be bored. Why be mac-n-cheese when I really need to be risotto?

Choosing the Least Incorrect Answer

Posted on by
Reply

My son was complaining to me the other day that he missed on question on a multiple choice quiz in his class and he got a low B grade instead of getting a perfect score. When I asked him why he was frustrated he told me, “Because it was easy and I missed it. But I think the question was wrong.” As usual, I pressed him further to explain his reasoning and found out that the question was indeed ambiguous but the answer choices were pretty obviously wrong all over. He asked me why someone would write a test like that. Which is how he got a big lesson on writing test questions.

Spin the Wheel

When you write a multiple choice test question for any reputable exam you are supposed to pick “wrong” answers, known as distractors, that ensure that the candidate doesn’t have a better than 25% chance of guessing the correct answer. You’ve probably seen this before because you took some kind of simple quiz that had answers that were completely wrong to the point of being easy to pick out. Those quizzes are usually designed to be passed with the minimum amount of effort.

This also extends to a question that includes answer choices that are paired. If you write a question that says “pick the three best answers” with six options that are binary pairs you’re basically saying to the candidate “Pick between these two three times and you’re probably going to get it right”. I’ve seen a number of these kinds of questions over the years and it feels like a shortcut to getting one on the house.

The most devious questions come from the math side of the house. Some of my friends have been known to write questions for their math tests and purposely work the problem wrong at a critical point to get a distractor that looks very plausible. You make the same mistake and you’re going to see the correct answer in the choices and get it wrong. The extra effort here matters because if you see too many students getting the same wrong distractor as the answer you know that there may be confusion about the process at that critical point. Also, the effort to make math question distractors look plausible is impressive and way too time consuming.

Why Is It Wrong?

Compelling distractors are a requirement for any sufficiently advanced testing platform. The professionals that write the tests understand that guessing your way through a multiple choice exam is a bad precedent and the whole format needs to be fair. The secret to getting the leg up on these exams is more than just knowing the right answer. It’s about knowing why things are wrong.

Take an easy example: OSPF LSAs. A question may ask you about a particular router in a diagram and ask you which LSAs that it sees. If the answer choices are fairly configured you’re going to be faced with some plausible looking answers. Say the question is about a not-so-stubby-area (NSSA). If you know the specifics of what makes this area unique you can start eliminating choices from the question. What if it’s asking about which LSAs are not allowed? Well, if you forgot the answer to that you can start by reading the answer choices and applying logic.

You can usually improve your chances of getting a question right by figuring out why the answers given are wrong for the question. In the above example, if LSA Type 1 is listed as an answer choice ask yourself “Why is this the wrong answer?” For the question about disallowed LSA types you can eliminate this choice because LSA Type 1 is always present inside an area. For a question about visibility of that LSA outside of an area you’d be asking a different question. But if you know that Type 1 LSAs are local and always visible you can cross off that as a potential answer. That means you boosted your chances of guessing the answer to 33%!

The question itself is easy if you know that NSSAs use Type 7 LSAs to convey information because Type 5 LSAs aren’t allowed. But if you understand why the other answers are wrong for the question asked you can also check your work. Why would you want to do that? Because the wording of the question can trip you up. How many times have you skimmed the question looking for keywords and missing things like “not” or “except”? If you work the question backwards looking for why answers are wrong and you keep coming up with them being right you may have read the question incorrectly in the first place. Likewise, if every answer is wrong somehow you may have a bad question on your hands.

What happens if the question is poorly worded and all the answer choices are wrong? Well, that’s when you get to pick the least incorrect answer and leave feedback. It’s not about picking the perfect answer in these situations. You have to know that a lot of hands touch test questions and there are times when things are rewritten and the intent can be changed somehow. If you know that you are dealing with a question that is ambiguous or flat-out wrong you should leave feedback in the question comments so it can be corrected. But you still have to answer the question. So, use the above method to find the piece that is the least incorrect and go with that choice. It may not be “right” according to the test question writer, but if enough people pick that answer you’re going to see someone taking a hard look at the question.

Tom’s Take

We are going to take a lot of tests in our lives. Multiple choice tests are easier but require lots of work, both on the part of the writer and the taker. It’s not enough to just memorize what the correct answers are going to be. If you study hard and understand why the distractors are incorrect you’ll have a more complete understanding of the material and you’ll be able to check your work as you go along. Given that most certification exams don’t allow you to go back and change answers once you’ve moved past the question the ability to check yourself in real time gives you an advantage that can mean the difference between passing and retaking the exam. And that same approach can help you when everything on the page looks wrong.

A Decade of CCIE Certification

Posted on by
2

I was notified this week that I’m eligible for the 10-year CCIE plaque. Which means that it’s been a decade since I walked out of Cisco’s Building C in San Jose with a new number and a different outlook on my networking career. The cliche is that “so many things have changed” since that day and it’s absolutely accurate because the only constant in life is change.

Labbing On the Road

I think the first thing that makes me think about the passage of time since my certification is the fact that the lab where I took the exam no longer exists. Building C was sold to the company that owns and operates the San Francisco 49ers stadium just down Tasman drive from the old letter buildings. Those real estate locations were much more valuable to the NFL than to Cisco. I can’t even really go and visit my old stomping grounds any more because the buildings were gutted, renovated, and offered to other operations that aren’t from Cisco.

Now, you don’t even go to San Jose or RTP for the lab. Three years ago the labs in the US moved to Richardson, TX. The central aspect of the location is pretty appealing when you think about it. A part of me wishes I would have had the opportunity to take the lab there since I wouldn’t have to jump on a plane and burn three days of my work schedule. The costs of my lab attempts would have been a lot less if I only had to drive down for one night in a hotel and got to come back and sleep in my bed that same night. I realize that it’s equally inconvenient for people to need to fly to the middle of the country when they used to be closer to the lab when it was on either coast. However, real estate in RTP and San Jose is beyond crazy when it comes to price. Moving the lab to somewhere more reasonable means Cisco is getting value out of their buildings elsewhere.

The mobile lab is another aspect of the changes in the CCIE certification program that are a welcome change. By putting the lab on the road and giving people in countries far away from a lab location the opportunity to get certified the program can continue to be relevant. This is due in large part to the changes in the lab that allow a large part of it to be virtualized or operated remotely from a rack located somewhere else. I remember starting my lab studies and thinking to myself that the rack that I was working on was just across the room. Not that there was much that I could do about it. The idea that there could be something going on that was just out of my reach was an itch I had to get over. Today, you would never even start to believe that you had a hardware issue in your lab because of the streamlining of the process. That can only happen when you optimize your offerings to the point where you can just virtualize the whole thing.

The Next Ten Years

Right now, I still have a year to go on my certification before I have to make the decision to keep it current or go to Emeritus retirement. My role on the CCIE Advisory council doesn’t matter either way. I’m likely going to just go Emeritus when the opportunity presents itself because I don’t use those lab skills every day. I’m not configuring BGP filter lists and port channels like I used to. The technical skills that I honed in Building C serve me more now to understand technology at an architecture level. I can see how people are using tools to solve problems and offer commentary when they are making poor decisions or when a better protocol exists.

The CCIE itself is still a very valuable certification to hold and study for. IT certification on the whole has been trending away from being the gold standard for hiring. Cloud and DevOps focus more on skills instead of papers hanging on a wall. However, operations teams still need ways to differentiate their people. If nothing else the CCIE is a great forcing function for you to figure out how deeply into networking you really want to get. It’s not enough to be curious about BGP or Frame Relay and traffic shaping QoS. You have to understand it at a level that would bore most others to tears. If you’re not prepared to know the minutia of a protocol the way that some people memorize batting averages or random movie trivia than you might not be up for this particular challenge.

The CCIE also isn’t going away any time soon. I remarked to someone the other day that the CCIE is a technology bellweather. I can remember the clamor to introduce the “new” SDN changes into the program so many years ago. I also chuckle when I think about the CCIE OpenFlow that more than a couple of people proposed. The certification program exists to refine and highlight the technology solutions that people are using today. It’s not a sneak peak at things that might be important later on in life. Think about how long it took for them to remove ISDN, ATM, and even frame relay from the test. And even frame relay was debated heavily because more than a few claimed they still used it in production.

The CCIE is a testament to the way that people study for and build networks at a high level. It’s not a cool badge to keep on your list like a hunting trophy. It’s a testament to the commitment that it takes to attain something like that. The JNCIE and the VCDX are much the same. They represent an investment of time and energy into something that proves your capabilities. More than any other certification, the CCIE challenges people. It creates study habits and builds communities. It makes people ask themselves hard questions about desire and commitment and helps the best rise to the occasion. It’s more than just a certification.

Tom’s Take

I wouldn’t change a thing about my CCIE journey. I learned as much from the failures as I did from the success. The opportunities afforded to me because of that number have been immeasurable. But through it all I realized that the process of getting my lab has helped shape me into who I am today. A decade past late night study sessions and soul-crushing failures I know that it was all worth it because it helped me take technology more seriously and form the habits and process that have served me well from then on. I’m happy to get the new plaque that marks me as a veteran of the lab plus ten years. My status as a CCIE might pass into Emeritus but the lessons I learned along the way will always be there.

Basics First and Basics Last

Posted on by
1

This week I found my tech life colliding with my normal life in an unintended and somewhat enlightening way. I went to a store to pick up something that was out of stock and while I was there making small talk the person behind the counter asked me what I did for a living. I mentioned technology and he said that he was going to college for a degree in MIS, which just happens to be the thing I have my degree in. We chatted about that for a few more minutes before he asked me something I get asked all the time.

“What is the one thing I need to make sure I pay attention to in my courses?”

It’s simple enough, right? You’ve done this before and you have the benefit of hindsight. What is the one thing that is most important to know and not screw up? The possible answers floating through my head were all about programming or analytical methods or even the dreaded infrastructure class I slept through and then made a career out of. But what I said was the most boring and most critical answer one could give.

“You need to know the basics backwards and forwards.”

Basics Training

Why do we teach the basics? Why do we even call them that? And why are people so keen on skipping over all of them so fast to get to the cool stuff? You have to understand the basics before you even move on and yet so many want to get the “easy” stuff out of the way because memorizing the OSI model or learning how an array works in programming is mind-numbing.

The basics exist because we all need to know how things work at their most atomic level. We memorize the OSI model in networking because it tells us how things should behave. Sure, TCP/IP blows it away. However, if you know how packets are supposed to work with that model it informs you how you need to approach troubleshooting and software design and even data center layouts.

I’ll admit that I really didn’t pay much attention when I took my Infrastructure class twenty years ago. I was hell-bent on being a consultant or a database admin and who needed to know how a CPU register worked? What was this stupid OSI model they wanted me to know? I’ll just memorize it for the test and be done with it. Needless to say that the intervening years have shown me the folly of not paying attention in that class. If I went back today I’d ace that OSI test with my eyes closed.

The basics seem useless because we can’t do much with them right now. They’re just like Lego bricks. We need uniform pieces with predictable characteristics to help us understand how things are supposed to work together. Without that knowledge of how things work you can’t build on it. If you don’t understand the different between RAM and a hard disk you won’t be able to build systems that rely on both. Better yet, when technology changes to incorporate solid state disks and persistent memory storage you need the basics to understand how they are different and where you need to apply that knowledge.

I once picked up a Cisco Press CCIE study guide for the written exam to brush up on my knowledge before retaking the written. The knowledge in the book seemed easy to me. It was all about spanning tree configurations and OSPF area types and what BGP keepalives were. I felt like it was a remedial text that didn’t give me any new knowledge. That’s when I realized that they knowledge in the book wasn’t supposed to be new. It was supposed to be a reminder of what I already learned in my CCNA and CCNP courses. If anything in the text was truly new, was it something I should have already known?

It’s also part of the reason the CCIE is such a fun exam in the lab. You should already know the basics of how things like RIP and OSPF work. So let’s test those basics in new ways. Any of the training lab you can take from companies like INE or Micronics are filled with tricky little scenarios that make you take the basics and apply them outside the box. That’s because the instructors don’t need to spend time teaching you how RIP forms neighbor relationships or adjacencies. They want to see if you remember how that happens so you can apply it to a question designed to stretch your knowledge. You can only do that when you know the basics.

Graduation Day

Basics aren’t just for learning at the beginning. You should also brush up on them when you’re at the top of your game. Why? Because it will answer questions you might not know you had or explain strange things that rely on the architecture we long-ago forgot about because it seemed basic.

A fun example was years ago in the online game City of Heroes. The players can earn in-game currency to buy and sell things. Eventually the game economy got to the point where players were at the maximum amount of currency for a player. What was that number? It was just over two billion. Pretty odd place to stop, right? What made them think that was a good stopping point? Random chance? Desire to keep the amount of currency in circulation low? Or was there a different reason?

That’s when I asked a simple question: How would you store the currency value in the game’s code? The answer for every programmer out there is an integer. And what’s the maximum value for an integer? For a 32-bit value it’s around four billion. But what if you use a signed integer for some reason? The maximum value is just over two billion in each direction. So the developers used a 32-bit signed integer and that’s why the currency value was capped where it was.

Over and over again in my career I find myself turning back to the basics to answer questions about things I need to understand or solve. We really want the solutions to be complex and hard to understand and solve because that shows our critical thinking skills being applied. However, if you start with the basics approach you’ll find that the solutions to problems or the root causes are often defined by something very basic that has far-reaching consequences. And if you forget how those basics work you’re going to spend a lot of time chasing your tail looking for a complex solution to a simple problem.

Tom’s Take

I don’t think my conversation partner was hoping for the answer I gave him. I’m sure he wanted me to say that this high level course was super important because it taught all the secrets you needed to know in order to succeed in life. Everyone wants to hear that the most important things are exciting and advanced. Finding out that the real key to everything is the basics you learn at the beginning of your journey is disappointing. However, for those that master the basics and remember them at every step of their journey, the end of the road is just as advanced and exciting as it was when you stepped on it in the first place. And you get there with a better understanding of how everything works.

How Long Should You Practice

Posted on by
1

A reporter once asked boxing legend Muhammad Ali how many sit-ups he did each day. I’m sure the reporter wasn’t expecting Ali’s answer. Ali replied with:

I don’t know. I don’t start counting them until it hurts. Those are the only ones that count. That’s what makes you a champion.”

Ali knew that counting things is just a numbers game. Five hundred poor sit-ups don’t count as much a fifty done the right way. With any practice that you do the only things that count are the things that teach your something or that push you to be better.

Don’t Practice Until It’s Right

People used to ask me how long I would spend at night studying for the CCIE lab. I told them I usually spent between five and seven hours depending on what I was studying. Sometimes those people would say things like “I’m not talking about setup time. I’m talking about actual lab work.” I always countered by making them explain why the setup isn’t part of the “real” work. That’s usually when they went quiet.

It’s far too easy to fall into the trap of overlooking things that you think are unimportant. A task you’ve done a hundred times is no big deal until you do it wrong the next time. Like Ali above, the things you do that require no effort don’t count. If you’re practicing a skill for a certification or a lab you need to put the same effort into it every time to ensure you’re doing it correctly. Lack of attention means you are doing it without gaining something from it.

I spend a lot of my time teaching things to people all over the place. I teach IT and networking skills to professionals. I teach outdoor skills to scouts of all ages. I teach merit badges and other things to a variety of youth. And I teach my kids life skills they will need. Every one of these lessons comes with instruction in the little details that matter. Every lesson also includes guidance that it needs to be practiced properly until it’s right. And then some.

Until You Can’t Get It Wrong

I tell my students and kids all the time, “Don’t practice until you get it right. Practice until you can’t get it wrong.” The level of involvement that it takes to get past the part where something finally works up to the level where it works every time is as wide as the gap at the lower end of the spectrum.

Too often people are content to work on something until they get it once. Whether it’s tying a knot or programming a router interface or even cooking a grilled cheese sandwich. Once you’ve done it right once you’re done with learning, right? Most of you are already shaking your head because you know that’s not right.

Once you get it right the first time you’ve already made a list of all the wrong ways to do something and you avoid them in the future. However, that list doesn’t include the entirety of all the wrong ways to do a thing. Amateurs make somewhat predictable mistakes because they’re working from the same basic knowledge. It’s when someone says they know what they’re doing that the real crazy stuff starts coming out of the woodwork.

Once you’ve practiced a skill you need to keep going. You need to work a variety of different angles to make sure you’ve covered all the ways you could get it wrong. If you’re tying a knot you need to practice with different kinds of ropes or in different positions. If there are two ways to tie something, practice them both. You don’t want to be an expert at a clove hitch over the end of a pole only to find out you have to tie it around the middle with no way to use the loop method you have memorized.

In IT, we lab things up to make sure we understand them. For these labs, try out the things in wrong ways. Click buttons before you’re supposed to. Put the wrong numbers in the field. See how the system will try to correct your errors. Maybe it doesn’t even bother? It’s easy to figure out you typed something in wrong when you hear a bell and see a message. It’s harder to troubleshoot when you don’t see anything right away and it all falls over later.

The extra practice above and beyond the first success is just like Muhammad Ali’s sit-ups. The hard ones count. The tasks that stretch your mind are the ones that build your skillset. You can’t give up when the answer isn’t right at your fingertips. Going that extra mile is the key to making yourself a better professional in whatever you do.

Tom’s Take

As we wind down 2020 we’re all looking to be better at things. Hobbies, skills, or professional talents are all calling to us to work on in whatever down time we have available to us. Make that practice count. Work hard to get it right every time. If you want to learn to make hollandaise sauce or write a novel or do a forward flip you have to keep practicing even after your success. Get to the point where you have no other choice but to get it right every single time. That’s the perfect amount of practice you need. Anything less counts as much as Muhammad Ali’s sit-ups before they start hurting.