Be S.M.A.R.T. Have a Goal.

I was recently speaking with a co-worker when she mentioned not having a goal for the first time in her life.  All throughout high school she told herself she'd buy a home, get a career, get a Masters etc. all before 25.  She accomplished these goals (and a lot more!), but now that she is past her target, she isn't feeling the same drive she did before.

I went through almost the opposite of this.  While I was working part time I had no goal.  I was content (or thought I was) to float around a bit.  Once this changed, however, things started picking up.  I earned Network+, then A+, then Security+ and Project+.  I enrolled in Community College and began picking up new skills.  While that was going on, I got a full time job and earned more responsibilities.  I believe all of this happened for a reason, and the reason is I finally had a target.

Stay on target!

 I am still not 100% sure what my target is.  My family will ask me what my 5 year plan is and I'll tell them something along the lines of running a Project team or managing a group, but beyond that I am not specific.  This is likely a weakness, as having a set goal has been amazingly beneficial.  In addition to this lack of 100%, iron-clad defined goal, one of the least-smart things I've ever done is answer "I don't know" when the Director of my department asked me what I wanted to learn and what my goals were.  I simply hadn't taken time to sit down and think about it.  My first goal was get back into IT, which helped me in getting certifications and my first part time IT job.  Past that, however, I lacked a true target.  I have since developed one, and that has allowed me to expand my skills, and my opportunities greatly.

Benefits of goal setting can be seen in many disciplines, from Business, to Fitness, to personal development.  Personally goals have helped me focus my energy and provide a more tangible reward for doing things.  This, in turns, helps to motivate me to set more goals and to strive to achieve them.  If there is one simple thing you can do to help your career in IT (or anything, really) take some time to think about your goals.  What do you want to be able to do?  Where do you want to be?  These don't have to be things that happen overnight, my goals are still in progress and I set them ~2 years back (and I'm sure I'll have more longer term goals, like buying a home).

Smart?

A great place to start is by being S.M.A.R.T.  This is a tool to help set goals.  This is just a guideline, but it will help to further focus your goal and help define how you may attain it.

Specific - You need to have a specific target, i.e. get a B+ or higher in C++.  Just saying learn C++ is too vague.

Measurable - You need to be able to measure your progress.  Not only will this help you track how you're doing, it will let you tweak what you're doing to do better.

Attainable - It has to be something you are actually able to accomplish.  Going from newbie to chess grandmaster in a year likely isn't attainable.

Relevant - It must relate in some what to your life and what you're doing.  If it doesn't, you may find it challenging to stay on target.

Trackable - It has to be something you can track.  If you don't know how well you're doing, how do you know when you got there?

Keep in mind this is just one place to start.  You may find other tools work better, or maybe not.  Take time to examine them, and then take time to develop a goal.  It will help you feel better about where you're at, and, more importantly, help you improve.

Do you know what YOUR goals are?

Please leave any questions in the comments and I'll be happy to reply.  Also, take time to go over your goals with your boss, friends, etc.  Their perspective can be incredibly valuable.

For assistance in setting a goal, check out Mind Tools, they have a good overview of the process.

IT Fundamentals : Never Stop Improving

It is better to move forward an inch then to stop.

~Chinese Proverb

Go little guy go!

Ever since I made the leap from office assisting to IT I have been in a constant state of improvement and development.  Whether I am learning how to build a computer in my bedroom (please PLEASE use anti-static pads if you do this!  The last thing you need is your cat zapping your motherboard... and keep your cat out of your work space.) or taking classes at a community college I have been developing skill sets.

Warning : Does NOT Mix Well With Computers

This has been both an intrinsic desire to learn how things operate and spurred by new job responsibilities (I have no clue how Microsoft Project works, but there's a class for that!).  I have found that by building time for the into my daily routine I am able to blend it into my life.  I know that after I get home I just need to spend half an hour doing homework, then I get to do other stuff (of course, this kind of back fires since if I'm not studying I feel antsy...).  I am fortunate that my current position highly encourages this. 

Now where is that note...

The biggest hurdle I had when I began doing this was where to get information.  The internet, as you may be aware, is a vast wilderness.  Part dumping ground, part hallowed shrine, part Mad Max, it can be hard to find what you're looking for.  Searching for "A+ Study" returns several million hits (fortunately some good ones pop up), the vast majority of which are rather useless.  The most success I had was with word of mouth.  A friend recommended Professor Messer (check him out.  Seriously, he rocks), which really got me started.  Taking time to examine information sources was also valuable.  Think of it like studying to study.

Once I got started, I was hooked.  I have borrowed books from co-workers, watched countless Youtube videos, taken classes, written papers, browsed hardware, tinkered with computers, fried circuits, dreamt about systems analysis (that was a weird night), and made hundreds, if not thousands, of note cards.  All of this drives towards the singular purpose of improving my skill set.
The trick is to choose activities which complement each other.  Taking a cooking class, then going to welding school may be interesting, but don't exactly support each other (unless you're cooking with a blow torch...)

This has several advantages, the biggest is I increase my value to my employer.  I have been able to take on increasing responsibility at work, mostly due to my new-found skills.  Simply learning how to learn has also helped at work since I am able to learn from my co-workers and take on new tasks.  Another big advantage is I feel better about myself.  I consistently find myself in new and interesting situations (not all are enjoyable, but they're all interesting...).  This keeps me out of a rut, which is a very dangerous place to be in.

To quote Dori, from finding Nemo:

Just Keep Swimming

Preparation Is Key : Informational Interviews

When I began getting back into IT I had no clue what to look for.  I didn't know what paths there were, what options I had for training, what to pursue with that training or how to get in the door.  Much of my time was spent answering those questions, and before I set foot inside a classroom or began to applying for jobs I interviewed.  I didn't interview for a job, I interviewed for information.

Information interviews were very important in getting me back into IT.  They began very small, cornering people I know who worked in IT (Programmers, Security Admins, Techs, etc.) and just picking their brain.

• What kind of skills do they have?
• Where do they work?
• How hard was it to get their job?
• Do they have any advice for a newbie like me?

Eventually, some of these first wave interviews turned into more formal affairs with their bosses or, when I really lucked out, their Director of IT.  Keep in mind these were not an attempt to get a job, or find an opening.  Instead it was just a sit down conversation about IT, and about how that person sees things.  I got a lot of contradictory advice (certification is bad, certification is good, get a degree, don't get a degree, get a degree if you want a degree), but I also  got a lot of really good advice.

• Are you more interested in Infrastructure or Applications?
• Are you willing to relocate?
• Did you know about various training seminars?

A big advantage of working part time was I could meet these folks face to face.  A good number of these interviews, however, were over the phone.  You would be surprised how many people are willing to spend ten or fifteen minutes talking to you.  Just be polite, respect their time and be prepared.  I went into every interview with a list of 10 or 15 questions, including:

• How did you get into IT?
• What skills do you recommend for an entry level technical position?
• What Certifications do you recommend and why?
• What certifications do you have, and do you find them useful?
• Do you recommend a degree in IT?
• Do you have a degree in IT?  Which one?  Do you find it useful?
• Is there anything else you think I should know as I am getting into IT?

(This list is by no means all inclusive.  Questions may not make sense in every situation, or new questions may come up.  As with everything don't be afraid to tweak it.)

These questions were designed to help me figure out what I need to do to get into IT, and where I should best apply my resources.  It also exposed me to different ways of thinking, as some folks found more value in Certification, or others had heard of new skills I should focus on.  They also helped me build up my ability to take an actual Job Interview.  It is very nerve wracking talking to someone who is doing what you want to do (especially if they're in management)!  

It you have the time (make the time) make some phone calls, send some emails and pound some pavement.  Get out there and see what other people are doing.  Remember, the goal isn't to get a job, or get setup to get one, it's just to ask questions and see what people think.

For me, I learned that I was more interested in Infrastructure (servers, tech support, etc.) than I was with Applications (programming, etc.).  I find this funny since I am now a Programmer Analyst, but at the time it helped me determine my entry back into IT.  It also gave me a good boost of confidence, now I knew what I was aiming at.  It gave me the direction to begin.

Preparation is Key : Job Interviews

Information Interviews, which are focused mainly on just helping you figure out what is going on and what direction to head.  They are very important in determining your next steps.  They are, however, mainly only used to help you figure out what to do.  A Job Interview is what actually gets you the job.

Job interviews can be scary.  They can be boring.  They can be long.  They can be short.  For me, they seemed to be all of those things.  I have been through three Job Interviews in IT, one for my volunteer position at Free Geek, another for my part time position, and a third for my current full time position.  They all had minor differences, but they all shared quite a bit.

What They Shared

Many things were similar between those three interviews.  I was asked why I wanted the job, what I had to offer, what I wanted to get from it, and what I expected.  I was quizzed on my technical skills, my work ethic and what I think of team work.  In general, they are going to try and determine if you'll be a good fit for their team.  They already have a working group, and they don't want to disrupt it too much by adding a loose cannon.

Definitely be ready to either demonstrate your technical skill (especially in IT), provide samples of your work, or answer questions about your skills.  They're hiring someone to do a highly skilled job (setting up AD accounts, coding Python, managing a team, whatever), and they will want to see a sample before they take you on.  If you don't know an answer to a question (or forget!) be honest, just let them know.  You'll never know everything, and they don't expect you to.

In all three cases, I also asked questions.  Not only are they gaining someone (if I were to be hired) but I would have to work with them.  There are a ton of guides on how to interview out there (take some time a read them!), but I always asked three questions, more if I had time.

• Whats the best part of the job.
• Whats the worst part of the job.
• Why do others enjoy working here.

All three questions gave me a good idea of what the company is like.  I never had anyone refuse to answer any of them (though they did try to minimize that second one...), although if they do it is likely a red flag.  If someone is unwilling to share with me what they personally dislike (or like) about a work environment I am immediately suspicious.  Regardless, definitely ask a few questions, not only will it help you learn about your potential job, but it will show them you are actually interested (also know something about the company you're interviewing with.  Google it.).

What was Different

Each interview took place in a different location, one in a back office, another in the only office and the third in a conference room where I was heavily outnumbered.  I took into consideration what environment I was walking into, and tailored my outfit to the best match I could think of.  For Free Geek I wore jeans and a t-shirt.  For the others, slacks and button down.  (Doing some recon before hand and determining what folks wear can be very helpful).

The formality was one of the largest differences.  Free Geek only took one interview, and I was told immediately that I got the position.  The part-time job had three interviews, one on the phone, another in person, and a third in person for technical questions.  The full-time position was one hour long interview with me and four others (a recruiter, a potential co-worker, my boss and his boss.  No pressure).

Definitely prepare for your Job Interviews.  Make sure you know how to get where you're going and leave plenty of time to arrive (I've gotten lost before, but was saved by having an extra 15 minutes).  If it is a technical position, be ready to answer questions or provide examples of work. And don't forget, relax!  They can be very nerve-wrecking, but if you're prepared and relax, you'll do the best job you can.

Tools for Success : Task Tracking

As I mentioned briefly in other posts, being able to keep track of what you are (and should be!) doing is very important.  On any given day dozens of individual tasks get thrown at me, and there is simply no way I will remember what I have to do and what steps are required.  There are some things, like resetting a password, or putting paper in the printer, that I don't bother writing down since they're "small", but almost everything else gets put into form of tracking tool or another.

GIGO (Garbage In, Garbage Out) applies to task tracking systems.  Systems are only as strong as their users discipline in maintaining them.  It is better to have a simple system that you maintain iron-clad regularity with than a complex one that you never look at.  Ensuring accurate information is input into the correct areas is paramount as the last thing you want is to look at it later and not know what it is talking about.

Ticketing Systems - Includes AutoTask, IssueTrak, etc.

Ticketing systems are basically databases that get filled up with various tasks.  Information you'll typically find includes who the ticket is assigned to, when it was made, who made it, contact information and a brief description of the problem.  These systems are generally only used in environments with larger numbers of individuals (i.e. companies).  One of the downsides is that individuals must invest time in maintaining the system (adding notes, updating information, routing tickets.  Many places have a single employee dedicated to managing tickets).  This time investment, however, will pay off as other individuals will be able to quickly and easily find and track information.  Metrics may also be generated, which are a great tool to help the team know where they're at (and to justify its existence to high powers!).

That was easy.

To Do Lists - Includes pen and paper, Astrid etc.

These are simply lists of things you need to get done.  To me, they are the simplest way to track tasks.  They rarely contain information other than the name of the task and (for me anyway) are either quickly handled or are passed off into a more robust system.  The main advantage of them is that they are easy to create (just grab paper and write) and can be made on an ad-hoc basis.  This is, of course, also a liability, since you'll soon end up with dozens of random lists floating around unless you maintain a strict process of managing them.

Custom Setups - Includes spreadsheets, bulletin boards, etc.

This is one of my more favorite methods.  I use a rather simple Excel spreadsheet to keep track of incoming tasks.  In addition to what i have to do, I also assign it a priority, start date, target end date and contacts.  I have found that providing myself with metrics on how long it takes to complete tasks of various severities helps me tweak the system in the future.

In the end it doesn't matter what you use, as long as you are consistent in it's application.  In addition to helping you keep track of what needs to be done, having a disciplined tracking system will allow someone to fill in for you if you are unavailable or on vacation.  It is also a valuable way to show your boss that you are actually working and not just beating the high score at mine sweeper.

Preparation Is Key : Career Planning Part 2

If I have learned anything in IT, it is that preparation is key.  Before meeting with a private customer for a job I must take time to go over what it is they need.  I need to know what tools to bring with me, what kind of equipment I will be dealing with, what software they have etc.  This also applies to situations at work, when I was working at the Help Desk I made sure I knew as much as I possible could about the person I was calling.  I would check and make sure they're computer was up and running, if there were any network wide problems, or if there were any recent changes.  In short, I did my homework.

The same goes for my path back into IT (part 1 here).  Free Geek provided me with a lot of hands on experience with hardware and with customer service.  Not only did it teach me how to strip down basically any type of desktop (Power PC's are a PAIN.  Apple did NOT want you opening those things) and deal with the surprises inside (food, cockroaches, bees, a hand gun once...) but it taught me how to handle a wide range of personalities and people in the context of IT.

Intel : Bees Inside

The experience I gained working with a large range of individuals was directly applicable to my next position at a small IT company.  They dealt primarily with small businesses providing "Break-Fix" IT Support.  Calls would range from setting up printing to physically moving a server to resetting passwords.  Most of the customers had what is called a SLA, or Service Level Agreement.  Basically these are contracts which outline the level of a support a customer can receive.  Level 1 may be 1 hour a week of remote, while level 3 may be 5 hours onsite support and unlimited remote support.  Level 3, of course, costs substantially more.

The vast majority of the work I did here was remote.  We used various tools, including LogMeIn (something I still use from time to time for my side gigs), and TeamViewer (This is a great one for family and friends since it's free for non-commercial use.  I help my grandfather out with this one). We also used a ticketing system to track what work was done and how long it took.  Learning how to use these tools was a bit of a learning curve, but it did teach me some valuable concepts, such as ticketing and remote support, which I had not yet been exposed to.

(I can virtually guarantee you that you will use a ticketing system of one kind or another in your path through IT.  I use it as a programmer analyst to track problems as they appear, our Help Desk uses it to track new installs, and our sysadmins use it to audit our permissions.  Having a systematic approach to tracking problems is a critical skill to learn.  I will get into this more in another post, but learn to love tickets.)

Start early.

This was also my first exposure to Microsoft Server and Active Directory (AD).  It was incredibly confusing and I got lost more times than I care to remember, but this trial by fire got me used to a normal business IT environment.  Simply looking at and navigating through AD helped prepare me for my first full time position.  I have learned that just by going through a system and getting a passing familiarity with it will pay off a LOT in the long term.  Be careful, but go in and play around! (with permission of course!).

From time to time I would have to go out on site.  This involved logging not only my time, but miles driven.  Currently the US Government mandates $.565 paid per mile driven for work, which made for some nice gas money.  Now this only includes times when work needs you to use your personal vehicle to go from site to site.  (It doesn't include driving into work in the morning.  It is especially nice for me since I happen to drive a hybrid and go "slow" at only 65mph).  These on site trips also gave me experience dealing with diverse physical systems.  No two customers were a like, even if their logical setup was similar.  Some have their server in a crawl space, others have no server, some have a large warehouse, others a coffee shop.  This helped make me more flexible and better able to adapt when presented a new situation (something that happens a LOT in life).

All the time I was working part time I was pursuing additional training on the side.  I finally earned my Network+, having started it when I was just volunteering at Free Geek, and began working on A+.  I was also still volunteering at Free Geek.  By this time I had moved into their "build" program and was getting good experience building computers from the mother board up.  I have kept up that habit of continually learning and improving.  Currently I am working on another security certification and am taking classes at my local community college.

My first (and only) part time job in IT taught me a lot.  Mainly, that preparation is key, and to keep moving forward.  By preparing myself a head of time for various situations, I was able to best capitalize on the opportunities offered.  Simply having a job was preparation for the next step in my IT journey, getting a full time job.  Being able to test out my skills and how I deal with problems gave me a better sense of confidence and more tools to use in the future.  Just like GI JOE taught me, Knowledge is Half the Battle (tm).

IT Fundamentals: Customer Service

Yeah sure, wake me up at 2 AM because your final doesn't print.

IT was never very far from me between College and my first IT job.  I was always being asked by friends, family and co-workers to fix little problems, or to advise them on which computer to get.  I think this consistent thought about various IT problems kept the spark going.  It did, of course, lead to some interesting situations (one guy threw his laptop down a hallway... another woke me up at 2AM for help during finals week).  It also helped shape how I think about IT, which is it is mainly customer service.

My first real boss (not mom or dad when I did chores) taught me one of the most important things I've ever learned about business.

Note: Not my boss.  The customers I would deal with. My boss was awesome.

If a customer is upset, or mad, they aren't upset or mad at you.  They're upset because they cannot get what they want.  And the good news is that you are the one who can help them get it.

I was working Point of Sale (POS) in retail at the time, and I would frequently have customers bust in and tear my head off (not literally thankfully) about finding XYZ part, or trying to return something.  In the beginning this was hard to deal with.  The more I thought about my bosses advice, the easier it got.  That advice completely removed me from the problem, and instead turned me into an ally for the customer, even if I was the source of the problem (forgetting to order some part, or losing an order).

The same holds true for IT.  Our customers are the employees at our business, our actual customers (for those of you doing break/fix), our family, our friends and others needing our assistance (another thing he taught me was never use "help".  "Help" implies there may be something wrong with them.  You "assist" people).  In my case, my current customer is the business I work for and it is my responsibility to assist the business in developing it's software.  When I was working part time in tech support my customer was whomever was paying the company for my services.

Percussive Maintenance at work

Regardless, I was the person who assisted the customer in getting what they want, whether it be a new RAID1 for their office, learning how to post on Facebook or squashing a virus.  In IT we deal with a lot of data, whether it be photos, tax returns or Futurama episodes.  To us, it's just data, but to that customer it is very important, and if anything threatens it they will get upset.  We also deal with expensive hardware, and no one wants to lose expensive stuff (of course if they're performing regular percussive maintenance.  

Our job working in IT, whether we're the newest Technician or the CIO is to serve the customer.  We will, of course, do this different when we are in different roles at work, but we are still responsible for providing quality customer service.  The hardest part for me is to just remember that I am not what is making the customer upset.

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.

Study Tools: Mnemonics

The easiest way to think about mnemonics is to think of them as mental shortcuts to help you remember something.  I have been using them for studying for a year or so and they are very helpful.  They do take a bit of time to get used to using, and there is some time investment required to build them, but the return you'll get outweighs that minor cost.

ROYGBIV is an example of mnemonic that most kids would recognize.  It's an easy way to remember rainbow colors (and one of the first things I can remember learning.  Actually, I remember one teacher writing

a                                                                          lot

on a black board to teach us not to write alot.  I can still remember what she looks like and how many other kids were in the room).  I actually have a bachelors in Psychology, so I won't get too into it, but just remember they're effective.

This is another one many people have seen.

There are actually world memory championships where contestants must do things like memorize a deck of cards in under two minutes.  They do this by practicing memorizing things.  This is not a skill unique to certain folks; anyone can do it with practice.

First you need to determine what you want to memorize.  As an example I'll use the formula for Schedule Variance from my Project+ training.  The formula is

SPI=EV/PV

For those of you who are curious, EV is Earned Value (multiply the percent of work done by the cost of completing that work) and PV is Planned Value (The planned cost of the work).

I could sit down and just repeat it over and over (a brute force method... Aka Drill and Kill).  Instead, I chose to develop a shortcut.  It is

eee vee pee vee schedule vee vee (spoken similar to easy peasy lemon squeezy).

Now a good thing to know is that mnemonics don't need to make sense to anyone else. Or even to you.  All they need to do is trigger a memory.  In thus case that phrase instantly brings the correct correct formula to mind.

Mnemonics don't need to be aural either.  Pictures are also a great way to remember.  For instance, the formula for Cost Performance Index (CPI) IS

CPI=EV/AC

Now the right hand side spells evac, as in evacuate.  So when I see CPI I visualize those letters on fire with a bunch of people running for their lives away from it.

If you see the CPI mushroom cloud, EV/AC!

Remember, the more vivid and full the mnemonics, the better it will serve you!

Once you've built your mnemonics begin using it with your note cards and other studying.  Soon it will begin to recall the info you need.  Eventually you'll just see the mnemonic in your head when presented with the trigger and you'll instantly know what it means.

Best of luck preparing, and please feel free to share your mnemonics below!

Study Tools: Note Cards

I have found that note cards are a great study tool.  I first started using them with Professor Messer's Network+ course.  First I would watch the videos and take copious notes on what was covered.  After that I would take those notes and then transfer the important points to some blank note cards.  From there it was an easy task of just going over them as much as I could.

There are really only three steps in developing this tool.  The secret is discipline.  You have to keep up on it. You must do a little every day and the overall effort will be immense.

The first step in the process is easy to do but takes a bit of practice.  All you have to do is read (or watch) and write down the important points.  The hard part is knowing what information to copy down.  The Sybex lines of books tend to italicize important points, and they also list exam related items at the end of the chapter.  Many books will do a similar thing and alert you to important ideas or definitions through boxes off areas on the page or other visual cues.  When I was using the Professor Messer books I copied over as much as I could write down about what he was saying (everything if I could get it).  This led to a lot of pausing the video so I could catch up with my writing.

The second step is also easy.  Just copy down the most pertinent notes from your first step onto your note cards.  I don't always write down every single note, some things I know I don't need to put onto note card format since I already have it memorized.  My general rule is to put it on a note card if I think it is important and if I cannot repeat the information with no cues.  This process can take a while since you need to re-format the information into a question on one side and then write the answer on the reverse.

The third step is also easy.  Just read the cards.  Read them a lot.  Every day.  Every hour.  Every spare moment you can find read the cards.  The more you go over them, the more they will stick in your brain, and that's the idea.  The key to success is the ability to recall facts, ideas and concepts clearly.

My current Project+ deck, note the business card. (and I'm only about 75% done!)

The biggest problem I have with note cards is simply the size of them.  I end up with stacks several inches high, and carting them all around town is a bit of a pain.  Fortunately, I have figured out some methods to combat this.

1. Do not make all of your note cards at once.  Instead, make them in sections.  Chapters of a book make for great sections.  Only carry one or two sections at a time.  Study them until you can answer every card, then switch up to another section.
2. Carry all your note cards in your bag, but only a few on you at any time.  Rotate out cards frequently to keep your brain guessing as to whats next.
3. Develop two, or more, decks.  Go through all your cards and set aside the ones you cannot answer immediately (My "Stumper" deck).  Take all the cards you know the first time and put them away for now (my "Easy" deck) and only carry around the ones that stump you.  Go over the first deck every other day just to keep it fresh, but focus mostly on the Stumper deck.  As you find yourself answering Stumper deck cards more and more frequently, move them into the Easy deck.  Once you only have one (a BIG Easy deck) you should be doing pretty good!

My stumper deck (right) and the easy deck (left).

The best part for me about this process is I get to spend time in coffee shops listening to music and relaxing.  I am furiously writing out note cards or focusing on reading, but at least I get to see a new spot and enjoy a nice cup of coffee (or tea).

The greatest strength of the note card is for facts.  Things like port numbers, types of contracts, OSI layers etc. are great.  More fluid concepts and ideas can be a bit hard to get on a note card, but at least it will get your brain thinking about these things regularly.

And the best part, 300 blank note cards only put me back $2!

Free Geek - Part 1

I have mentioned Free Geek in a few posts and figured I would expand on them!

Free Geek, at its core, is a hardware recycler.  I found it in Portland, Oregon, and was fortunate enough to get a spot as an intern at the Help Desk.  I am honestly surprised I got the spot since I had no recent IT experience going into it.  Fortunately Help Desk is basically just customer service, something I am rather good at.  And even better, they provided on the job, hands on training for everything I would need.

Free Geek accepts donations of used (in basically ANY condition... they've found beehives in donated hardware before...) electronics, computers and basically anything with an on-switch.  From there, they either reuse components if they work, or if they don't they get broken down to their components and recycled (did you know that a ton of computer waste has more gold in it than a ton of earth from a gold mine?).  Re-used components are either reassembled into new, usable computers running Ubuntu, or are sold in their thrift shop for cheap.

Volunteers can earn up to one free computer a year, either by building 5 computers or by volunteering for 25 hours.  They accept volunteers of almost any age (minor children need an adult guardian with them.  I saw several pairs as I was there and though it was a great way to bond and support kids), and provide them with one of three routes:

• Recycling
• Building
• Interning

Working in recycling basically means you rip apart old stuff and sort it for disposal.  I went the Intern and Build routes, but I always through recycling looked like fun.  Depending on your physical ability you can do things like rip printers apart (they're not meant to be disassembled), tear down computer chassis or do less strenuous tasks like break down keyboards.  Not much ends up in the trash, they are able to recycle the plastics and metals... sometimes at a profit.

Building was a lot of fun for me.  They start you at a bench and teach you the basic parts of a computer (RAMBUS vs. SO-DIMM, CD-ROM vs. Hard disk etc.  It's very basic, but an excellent spot for a beginner to start).  After you can identify all the component pieces they move you onto pre-build, which is where you disassemble computers.  Lots of vacuuming is involved! (if you've ever opened a 10 year old computer you know what I mean ).  Once it's (relatively) clean, you simply follow a really long flow chart to determine what can be re-used.  Basically only stuff that's 1-2 years old is kept, everything else gets moved to recycling.  Any components which are damaged (blown capacitors, bent pins etc.) get sent to Advanced Build to be tested and repaired.  Everything else that is kept is tested and then used in Build.

Build is the next stage, and teaches you how to perform Quality Assurance (QA) and to build computers from (almost... the CPU and motherboard are already in place) scratch.  They have developed a great checklist which teaches you how to put everything together.  Given the odd assortment of franken parts sometimes you just have to try different combinations of components before things work (frustrating!).

Once you've built 5 computers you can, if you wish, go onto Advanced Build.  Advanced Build is not something I did, but it looked very interesting; you can work on Macs, servers, test electronic components, rebuild motherbuilds etc.

That's all for for now... stay tuned for more information on their Internships!  And definitely check out their website.

Preparation is key : Career Planning Part 1

It had been 6 years after leaving IT in college before I finally made the leap back into it.  In the mean time I did nothing IT related.  I worked for a small business working in their office.  My IT experience in those years was mostly restricted to fixing a jammed printer or removing the occasional virus.  I am not sure what finally flipped the switch and pushed me back into IT, but I have some ideas:

• A desire to learn something new
• Wanting more money (Part time doesn't exactly pay a lot)
• Wanting a greater challenge
• Wanting to be around technology

Regardless of the actual reason, I began looking at different paths to get back into IT.  I was fortunate, in that there was a local computer recycler called Free Geek near me.  They have multiple offerings in the way of volunteering, everything from their receiving dock to interning at their Help Desk (i'll write more about my experience there in another post).

Through some miracle (seriously, I had had NO IT experience in the past few years) I landed a position as an unpaid intern at their Help Desk.  I worked 8 hours a weeks, in two four hours shifts.  All the training was hands on and on the fly.  I learned everything from some Linux command line to how to field a call to how to build a computer from nothing.  True, I had some of these skills before, but getting the opportunity to work with other nerds was a huge boost.  In addition to this internship I also volunteered building computers, which gave me a solid base for my certifications.

After a month or two of volunteering I began looking for a paying IT gig.  I submitted dozens of resumes to Craigslist ads, and several directly to companies (Nike and the like).  The only reply to any of them was a phone interview which turned into a part time job working at an IT consulting company.  It was tiny, a handful of employees, but it paid!  During this time I had begun to study for my Network+ (a friend had a copy of the book so I started here instead of A+, where most folks start.  Also, Professor Messer was, and still is, a godsend!), which I obtained in November of that year.

This job, like my previous one in an office, was also part time.  This was nice since it allowed me a lot of time to study and pursue other pursuits, but it still wasn't enough.  The company I was with still wasn't offering me enough, it was simply too small.  I began looking for ways to expand; I was still volunteering, not interning anymore build working in their Build program, and finally found an IT recruiter who helped me out...

Stay tuned for Part 2!