What's after A+? Or 70-680? Or CCNA? Or (fill in the blank) certification?

I'd wager you did the same thing I did when I got into IT.  I earned a certification, looked back, and wandered what to do next.  I chose to continue earning certifications, but many folks take what they have and run with it.

Yup, all done!

The answer to that question depends entirely on what someone wants to do with their IT career.  I chose Network+ then Security+, both also offered by CompTIA.  Like A+ they are both more focused on high level concepts and ideas within their realms.  They have provided me with a good foundation to build more skills on top of, and are broad enough that I can apply them in most situations I find myself in.

The wonderful, and less-than-wonderful, thing about IT certifications is there are a lot (Googleing IT Certification returns 64+ million pages).  Many, many organizations and companies offer certifications on their hardware, software and methodologies.  The challenge you face is which one do you want to pursue?  You is to sit down and determine what path you want to take.  Hardware or software?  Administration or network engineering?  Programming or management?  Or some other combination?

Another, equally important question, is what do you want to do?  Does it make sense to earn your A+ if you are going to become a programmer?  Will your current or future job make use of the skills you learn, or is this just something you want to do?

The trick is to figure out what you want to do, what will help you get there, and then, as Nike says, Just Do It.

For those of you interest in Microsoft certifications there are MANY paths to take!  Microsoft offers certifications for Technicians, Server Administrators, Programmers and more.

CISCO also offers certifications on their hardware.  If you are interested in network engineering, these are a great place to look.

CompTIA has an extensive line of vendor-neutral certifications.  I personally found them a great place to get started and helped give me a broad knowledge of IT.

Study Tips : Shorthand

I'll start this off with saying that my hand writing is awful, may worse than Doctor awful.  This, combined with the large amount of handwritten notes I take led to me developing a good number of shortcuts when writing.  These short cuts have helped speed up not only my note taking, but the speed at which I can make note cards (a very boring task at times!).  It also cuts down on the quantity of paper I have to use to contain everything.

There is training you can get on actual shorthand.  Secretaries and others taking tons of notes utilize it to write quickly and accurately.  I have not gotten into any of it, although I was much more interested when I was still taking hand written notes.

Unfortunately if you are sharing your notes or cards with anyone, these can make it quite challenging for them.  I have shared my cards with co-workers and have had to spend some time teaching them my short cuts.  The thing to keep in mind is that it doesn't matter what shorthand you use, just be consistent with yourself so you don't get confused.  There are a few shorthand shortcuts I use that have confused me (Auth can mean either Authentication or Authorization... oops) which I have had to go back and change.  It did take a bunch of discipline to un-learn.

Just like Mnemonics, your short hand doesn't have to make sense to anyone else, and it doesn't have to make sense out of context either.  Just be careful that you setup symbols and shortcuts that you will remember.  Even draw up a list, print it out and use it until you remember them all.

Moving on to some suggestions for short hand!  Remember, it doesn't matter what you use, just be consistent with what you use, and be open to change.

@ = "At"

Replace the word "at" with the "@" symbol.  This was one of the first ones I figured out, mostly since we all use it daily with email addresses.  The symbol is quite fluid when handwritten, so while replace "at" with a similarly sized symbol I find it easier to write.

"-/"  =  Not

I use this one frequently.  I remember it from a predicate logic class in college.  Basically it means "not" (whatever comes next), or "opposite" (whatever comes next).  So if I write "The light should be -/red" it would mean the light will be any color but red.

Pcol = Protocol

Replace the word "Protocol" with Pcol.  I haven't seen any word ever in English (which I am less than skilled at) that starts with Pcol, so it's unlikely you'll mix this up with anything.  I used this one a LOT when I was working on Security+ (there's a ton of protocols to understand), and am continued using it in Project+, although not to the extent I had.

Msg = Message

Using "Msg" instead of Message.  This one is a bit more widely used (at least in some of the games I have played in the past).  It showed up a bit more in Project+ than the others, but still shows up.

SVC = Service 

SVC popped up in all the certifications I've taken.  When I use it I tend to put it in all caps just so I know it's the short hand.

SVR = Server 

SVR also showed up in all the certifications I've taken.  Servers also show up a lot in IT (shocker, I know) so I have kept using it in notes at my current job.  This is another one I try to keep capitalized.

Dest = Destination 

Dest found it's life mainly in Network+ and Security+.  

Nwork = Network

Nwork came about in my first Certification, Network+ (also a shocker...).  I've used it fairly consistently in my note taking, not only for technical stuff but for other functions as well.

Sec = Security

I began using Sec during my Security+ training.  It took some getting used to to remember this one (I am not sure why) but it certainly came in handy.

Auth = Authentication... OR Authorization

This one was dangerous.  The terms "Authentication" and "Authorization" came up a LOT in Security+ and I kept forgetting which one Auth meant.  I mainly began using contextual clues to tell me which one it should be.

HW, SW = Hardware and Software

I started using these when I began taking inventory at one of my older jobs.  I began to circle them so I knew they were short hand, and it's stuck with me.

Certifications: Some Thoughts

A large part of my entry back into IT was earning certifications.  The short version is that between my certifications and my volunteering at Free Geek I was able to get a job back in IT relatively quickly.  I was fortunate and had my first certification almost land in my lap.  A friend had a copy of the Network+ book, and he recommended Professor Messer.  Between the two of those (and about 200 note cards) I had my Network+ in hand relatively quickly.

Moving on!

I won't get into detail about different certifications too much, instead I will just share my thoughts on them.

There are two main theories behind certifications:

Big help, that certification..

1. They are not worth the time since an employer is looking for experience and skills, not 3rd party certification.  

I would never trust an uncertified Ninja.

    2.  They are an external way to validate skills and give people confidence in your abilities.

I subscribe to a mix of both these theories.  I believe that certifications are required to get you foot in the door.  I certainly wouldn't take my car to a mechanic who wasn't certified by Honda or another agency.  Neither would I take my cat to an un-certified vet.  How then can I expect a potential employer to take a  serious look at my resume?  True, someone may vouch for me, or I may have the chance to prove my skills, but having CompTIA, or Cisco, or PMI backing me up carries a lot of weight (it also increases the pressure a bit!).  

Of course, I need to be able to back up that piece of paper with the skills.  Certification, to me, is a foot in the door.  It tells someone I have the discipline and drive to get that piece of paper saying yes, Robert can do what he says.  The next step is proving myself.  This is where I agree with Theory 1 above.  Even with my A+, I still need to keep my skills up.  I can't just stop practicing and sit back.  I need to show whoever is interested in me that I can do what my certifications claim; it is a potent combination when you can blend certification and skill.

This is not to say you cannot or will not find a job  just having skills, or just having certifications.  Indeed, I know several individuals who are very skilled at technical services who are happily employed.  I also know a few individuals who have certifications just to have them.  In truth, it is up to you to determine which path you want to take.  Personally I have found a mix to be the best combination, but there are certainly opportunities for any combination of the two.

I began my journey into IT with Network+ purely by luck.  A combination of Network+ and volunteer experience landed my first job.  From there I got more hands on experience working in Tech Support (and on servers!), and more certifications (A+, then Security+).  The growth of my hands on skills and the growing list of certifications kept me moving forward at work and has helped ensure I am consistently getting new experiences to grow with.

There is no right or wrong way to go about IT.  Find what works for you and go with it.  Just keep in mind, you may run into people who ascribe to a different philosophy.  Just smile and tell them what has worked for you.  They may have a differing opinion, but that's their path.  Follow yours.

Certifications: CompTIA Network +

After A+ many folks go for CompTIAs Network+.  In the same way A+ covers the basics if how computers operate, Network+ covers how networks operate.  Some network questions appear on A+, but it only covers the bare bones basics.  Similarly to A+ it does not cover many technical skills (most of the technical knowledge covered is just some basic command line stuff like tracert and ping), but instead focuses on overall knowledge of networking.  If you are interested in pursuing it I highly recommend Professor Messers great series of videos explaining every part of the exam, as well as the Sybex line of books (I have had good personal experiences with this particular brand, but there are many options out there!).

As with most examinations I have had, the single most challenging portion for me was memorizing seemingly useless information.  Quick, what does TCP port 21 do normally?  What is 10baseT?  I find that kind of information to be mostly make work as in the real world I can Google it (and I do!).  Just like A+ flashcards were my friend for the drill and kill information.  That said, you MUST know all the Port numbers, and the differences between cabling (at least for N10-004, the Network+ certification I hold.  Currently they are on N10-005, which may have slightly different requirements!).

Quick, what kind of network is this?

Definitely know the different kinds of network topologies, as well as the differences in network hardware.  I found it very useful to look at real network maps to understand how some of the components can interact with each other.  Knowing network security was also important.

This exam is linked with A+ and Security+ for expiration dates; earning one will renew the others.  I didn't figure that out until I earned my Security+ which was a nice surprise.  Many folks dislike the fact that certifications expire, but technology is always changing.  An A+ from ten years ago may be viewed as largely out of date (token ring? whats that?).  Not all of the information will be stale, especially if you keep up your job experience, but it is still out of date.

Network+ is an excellent bridge into the CCNA offered by Cisco (not something I think I will pursue since I hear it locks you into Cisco a bit and is rather technical in nature), and is excellent for Security+ as well.  Overall it is a great certification for someone looking to get into Network Engineer or Administration.  The A+, Network+ and Security+ form a bit of a triumvirate of basic IT knowledge, having all three will help round you out.

Study Tools: Note Cards Part 2

Being stuck on a plane for several hours recently I've put some more thoughts into how to use note cards to study.  Check out my previous thoughts on note cards for a starting point.  

When I was first studying for Network+ I would label each card with the portion of the exam the information relates to.  I would put the Objective number (i.e. 1.8 for DNS information) in the upper right hand corner of the front of the card.  I kept them all grouped by Objective.  Since then, I have dropped the Objective number from the card just to see how it changes how I use the cards.

An example of the front of my note cards with the Objective.

The advantage I have found in having the Objective is it allows me to study specific portions.  This is great because I can target my studying to areas that I am not doing as well in.  Of course, the trick is figuring out where your weakness is.  The Sybex books generally contain a CD with bonus content (practice exams, note cards etc.) which I have used to figure out where I'm weak.  There are also some practice exams online, the problem is you never know if they're all that accurate.

And the back

The problem I have found in having the Objective on the card is it distracts me from the information on the card.  Instead of focusing entirely on the question or answer, I am also thinking of the Objective number.  None of the exams I have taken have ever made mention of the Objective number during the exam.  Many exams will give you a readout of the areas you missed at the end.  They don't tell you the answers, or even the specific questions you've missed, but they give you the Objective number and a description of that Objective.  e.g. 3.2 Categorize standard connector types based on network media.

In addition to having the Objective on the card (or not!) I have begun to randomize the order I have the cards in.  For Network+ I kept all of the cards grouped by their Objective, all the Objective 1's were in a group, all the 2's in another etc.  For Project+ I kept shuffling the deck as I put together smaller stacks.  Once I could do most of the stack I would shuffle it into the rest of the deck.  I still pull out all of the Stumpers, but I keep them as mixed up as possible.  All the exams I have taken randomize the questions, so you never know which Objective is first.  I figure if I study that way it will make me better on the exam.

Certifications : CompTIA A+

By far the most common certification I have seen requested is A+.  A+ is the bread and butter of the computer technician.  It covers everything from motherboard design and layout to how to troubleshoot printing.  CompTIA, the Computing Technology Industry Association, is an independent group that provides certification on a wide range of topics including servers, projects, health IT and more.  Their certifications tend to be more on overarching topics and general knowledge than specifics (i.e. complex command line sequences).

A+ is generally recommended as a starting point for certification (Through dumb luck I started with Network+, which focuses more on networking).  Many employers require it for entry level, and many others require it of their administrators just to keep them current.  You should know that it does require re-certification every 3 years as technology changes.  This requirement ruffles some folks feathers, but to me it makes perfect sense.  I wouldn't trust a mechanic who didn't prove their abilities to repair my car, why are computes any different? (In many ways they are more valuable, think about how much data lives on computers in our daily lives).  Fortunately if you get another "related" (Network+, Security+ or CASP) it will update the expiration date to three years from the most recent certification.

The A+ certification is actually composed of 2 exams, the practical and the theory.  You must pass both to become certified.  The practical focuses more on troubleshooting and customer care, while the theory portion focuses more on how computers operate and what makes them tick.  CompTIA suggests 500 hours of hands on work with computers, although a driven user should be able to handle these exams fairly easily. The more experience you can get hands on with hardware and computers the better.

By far the best resource for this course that I have found is Professor Messer.  He has a series of excellent online training videos which go over every aspect of them exam.  He will walk you through everything you need to pass the exam.  I have found that a combination of note taking (writing every bullet point from every slide of every video) and flash cards (generating flash cards based on my notes) led to my success with this certification (90% on both exams, and not a penny spent on training!... except the flash cards).  Of course, if you like you may pay Professor Messer for a downloadable copy and some more excellent stuff.

Overall this certification is a great place to begin, and something that provides a solid foundation to any IT career.