-
We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.
A+ Certification?
- Thread starter monte84
- Start date
Most certs are lame (some exceptions). I had to get mine for a job because clients demanded our techs be certified in something. So of course, we all got the easiest cert we could. I am pretty sure it had very little effect on our service levels, but of course the customer is always right 😀
Schadenfroh
Elite Member
hardware part is sooo easy, but the software part can be tricky i reccomend studying for the software
TheToOTaLL
Platinum Member
Non-CC PayPal waiting 😀
IamElectro
Golden Member
The only certification I can think that would be worth having is the "CCNE" but passing the final exam is like taking your medical boards, and you have to be recertified every 3 years.
CCNE "Cisco Certified Network Engineer"=6 figure income
CCNE "Cisco Certified Network Engineer"=6 figure income
Its not that bad if you've got a voucher and are only 17-18 and want to work at a half-decent computer manufacturer 😀 I am going to study up for one soon. When I leave high school I should be done with CCNA. Depending on where I go with computers, should I go for networking? Hardware? Programming? Anyone have any suggestions?
Personally, I'd say go for the certs. If nothing else, it gives you some focus to your studies. It also shows a prospective employer that you have accomplished at least some basic level of expertise. The down side is that the market is still "sorta' flooded with other people that have done the same thing (studied, no "real" experience) ... and more-to-much-more (there are still CCIEs out there looking for a job).
Where I believe most new networking folks screw up is that they only study for the test. IMHO, you do much better if you "read & bleed" - work on studying the scope of the test .... but try to gain some depth to the knowledge by killing and fixing the machines, tech the concepts you're learning to someone - teaching is one of the best ways to learn. The reason I say that is that you present some point: the person you're instructing will ask "Why is this done like that?" - and if you don't know, you got another topic to research.... or perhaps work through the question together and try to figure it out, THEN do some research to see how accurate you are.
There's a fair amount of basic head-scratching in the beginning, learning one topic frequently gives you the basis of learning / understanding other topics or concepts. The more you gain basic understanding, the easier it becomes to figure out the harder stuff.
If you only study for the test, all you know are a bunch of disconnected facts that are frequently useless in the practical world.
For nearly evey job you apply for, one or more of the senior guys are going to sit down with you and ask questions, or present problems; they will not be multiple choice questions - they're going to be looking for basic understanding and troubleshooting skills. They're going to be looking for how well you can solve some typical prolems.
As far as getting experience, there are a number of volunteer roles where you can help, learn a little, and boost your resume. Places like churches, retirement communities, shelters, schools, etc. ANY hands-on in a "real world" organization will improve your chances of getting hired. If there's some "Mom & Pop" computer stores in your neighborhood, apply for a job there part-time ... regardless of the pay...regardless of the job; the experience is worth the price and the other technical types are usually able to give you some practical background.
Some places may even hire you "for barter;" you work so many hours and get some hardware or software in return. It's a good deal for them - they get cheap labor - and it's a good deal for you - you get real experience and maybe some new toys.
To pull this back to the topic: once you feel that you have some study and practical background that relates to a test, take the test. Doing brain dumps, crib notes, and boot camps may get you through the test, but you're still (frequently) useless in a "real world" job ... and that's easily discovered in the interview.
Another way to get to know the nuts & bolts of the system (computer, OS, application, or network) is to learn programming - any programming - (scripting, batch files, BASIC, C, whatever) that works with the basic system resources. Learning BIOS calls, TCP/IP functions, and Remote Procedure Calls will do alot for your understanding of how a system works. Much of routine system administration involves automating / programming / scripting the repetitive tasks.
Pardon the ramble. I've been in the industry twenty-something years, I've seen some well-trained idiots, I've seen some sparsely-trained natural-born techs, it's better to not know (but can figure it out or find it out) than to be able to pop out an answer you can't decide how to implement (or not know how it applies). Strive to learn as much as you can, not just one-answer-out-of-four. Get your hands on some systems any way your can.
.02
Scott
Where I believe most new networking folks screw up is that they only study for the test. IMHO, you do much better if you "read & bleed" - work on studying the scope of the test .... but try to gain some depth to the knowledge by killing and fixing the machines, tech the concepts you're learning to someone - teaching is one of the best ways to learn. The reason I say that is that you present some point: the person you're instructing will ask "Why is this done like that?" - and if you don't know, you got another topic to research.... or perhaps work through the question together and try to figure it out, THEN do some research to see how accurate you are.
There's a fair amount of basic head-scratching in the beginning, learning one topic frequently gives you the basis of learning / understanding other topics or concepts. The more you gain basic understanding, the easier it becomes to figure out the harder stuff.
If you only study for the test, all you know are a bunch of disconnected facts that are frequently useless in the practical world.
For nearly evey job you apply for, one or more of the senior guys are going to sit down with you and ask questions, or present problems; they will not be multiple choice questions - they're going to be looking for basic understanding and troubleshooting skills. They're going to be looking for how well you can solve some typical prolems.
As far as getting experience, there are a number of volunteer roles where you can help, learn a little, and boost your resume. Places like churches, retirement communities, shelters, schools, etc. ANY hands-on in a "real world" organization will improve your chances of getting hired. If there's some "Mom & Pop" computer stores in your neighborhood, apply for a job there part-time ... regardless of the pay...regardless of the job; the experience is worth the price and the other technical types are usually able to give you some practical background.
Some places may even hire you "for barter;" you work so many hours and get some hardware or software in return. It's a good deal for them - they get cheap labor - and it's a good deal for you - you get real experience and maybe some new toys.
To pull this back to the topic: once you feel that you have some study and practical background that relates to a test, take the test. Doing brain dumps, crib notes, and boot camps may get you through the test, but you're still (frequently) useless in a "real world" job ... and that's easily discovered in the interview.
Another way to get to know the nuts & bolts of the system (computer, OS, application, or network) is to learn programming - any programming - (scripting, batch files, BASIC, C, whatever) that works with the basic system resources. Learning BIOS calls, TCP/IP functions, and Remote Procedure Calls will do alot for your understanding of how a system works. Much of routine system administration involves automating / programming / scripting the repetitive tasks.
Pardon the ramble. I've been in the industry twenty-something years, I've seen some well-trained idiots, I've seen some sparsely-trained natural-born techs, it's better to not know (but can figure it out or find it out) than to be able to pop out an answer you can't decide how to implement (or not know how it applies). Strive to learn as much as you can, not just one-answer-out-of-four. Get your hands on some systems any way your can.
.02
Scott
That right there is one of the best things I have ever read on ATOT
All to often there are people who chase that piece of paper and fail to actually learn anything.
I have limited "education" in electronics BUT I will go up against most "COLLEGE TECHS" any day because I learned HOW TO FIX IT by understanding the basics of logical troubleshooting.
Its all about problem-solving. I only took half the a+ (hardware) and i've been handling everything computer-related (network and beyond) for a company for over a year. I don't know what I'm doing sometimes, but I'm able to figure it out. I'll probably end up getting certified in a few areas to validate my experience.
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 25K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes + WCL Discussion Threads
- Started by Tigerick
- Replies: 25K
-
Discussion Intel current and future Lakes & Rapids thread- Started by TheF34RChannel
- Replies: 24K
-
-
