Upgrading Training and Certification?
"I checked out just about every 'school' offering training and placement in the New York City area, and frankly each of them almost had me running screaming into the night. Atrocious facilities, hot, stuffy, cramped classrooms and teachers whose every other words are 'memorize this--it will be on the test.'
Most places were shocked when I said I didn't care about certifications and exams. I explained that I need not just the theory but some hands-on experience with hardware that I don't have access to at home, and knowledge sufficient to at least get me something entry-level once again.
I learn best by demonstration and instruction so CBT CD-ROMs and 'go-read-a-book' aren't viable options for me. Since I'm not currently employed, I also need some form of placement assistance as well. Frankly, I didn't think this was too much to ask for until I really started looking. I looked at Learning Tree specifically, but their policies are strictly business-to-business training, not to individuals."
I recommend purchasing a 1700 router and/or a 2900 switch from ebay. You can set up configurations, learn the CLI and play around. Flash the rom, reload the O/S. All that. The cost is less - be patient and you can get a 2900 for less than $400 like I did.
After the test you can resell it for what you got or you can keep it and use it in your home. Can't do either with a class.
. This sig unintentionally left blank. I meant to put something here, but I'm busy.
I found that registering a business name and a business license is the _best_ form of certification.
Certification means "To confirm as genuine". People are more apt to believe someone with a business card can fix their computer woes than a stack full of resumes littered with acronyms (CNE, MCSE, CCNA, A+, WYSIWYG, ad infinitum ad nauseum)
If you know your stuff and can fix a clients problem, it doesn't matter what your certification is. All people want are results.
Ruby on Rails Screencast
I went through a turning point in my career some time in 1998. I was a Novell CNE, and it became obvious to me that I needed to get an MCSE to stay competitive in the systems administration/integration job market. And so I set out to do so.
I knew enough about Novell to see the stupid games commercial software vendors play with each other at the expense of the customer and the sanity of consultants hired to make sense of the mess. Starting on the MCSE training track was sufficient to raise my level of disgust to the point that I began questioning my career. My impression was that the industry was soulless, that hard work was not rewarded, and that the only way to make money in the business was to take advantage of customers and profit by their ignorance.
Just as I was thinking of opening a restaurant, the nagging love that I'd always had for working with computers took hold, so I set myself to the task of reinventing myself.
I'd started playing with Linux just a few months before, and was hopelessly inept, but found that it had rekindled my love for working with computers. Up to this point, however, I'd never considered it more than a hobby. I remembered, however, that my original decision to pursue IT was not a matter of economics, but because I really loved it. I got into computers because of the joy of programming on my C64. Long before computers were cool; long before I even knew I could make money working with them, I loved them. I realized that my hobby with Linux was in keeping with my beginnings in computers, but that I'd been restricting the time I spent with it so that I could keep up with the latest interopability problems with Groupwise and Exchange.
I already knew I couln't go to another training class; that I couldn't pick up another trade rag; that I couldn't spend the rest of my career begging support reps to tell me the secrets of making shit work that are known only in internal documents, protected by inane marketing concerns. So despite how stupid a move it seemed at the time, I had no choice but to spend my downtime studying Linux. I started my career following my interests, and I knew I had to keep doing so.
Then, the bottom fell out of the IT industry. In 2001, the company I was with was absorbed by another one, and in the process about 90% of the original staff was eventually hemorrhaged. I saw the writing on the wall before it really got bad, and managed to round up enough solo Linux work to get out while they were still in the mood to beg me to stay. I refused. I did solo Linux consulting for a while, then landed a hot job with a very successful network outfit. I now work exclusively in Linux, writing network automation scripting and performing enterprise security audits. I've remained employed throughout the recession thus far, and my income has steadily increased.
Do what you love. The rest will follow. Life's too short to deal with bullshit.