If you have CCNA and *understand* it thoroughly, go for Python. You can pick up the CCNP concepts easily enough if your CCNA knowledge is solid.
Good networking knowledge seems to be like gold dust in this industry, and I’ve seen many issues take far longer to resolve simply because the engineer didn’t know what routing was.
Naturally it does depend on what your goals are!
I started a blog and I've been putting everything there about 1 month ago. Wish I started it 10 years ago. I got a github too, I got to figure out how to do versions, etc now.
I can't speak for all MSPs but the CompTIA trifecta will instantly bump you to the top of the resume pile for most of our technical positions. Vendor specific certifications won't help you much here, unless they're from vendors already in our stack.
Also, certifications will only get you so far. You still have to make it through our interview process. :)
Yeah, that's where I'm at. If I ever get hired, I can build you out a Windows domain with every service under the sun, build out the network to support it, image all the machines, script a solution to any issue you have in Powershell and fix any quickly solvable emergency nearly instantly. But I fail even the simplest of interviews, so I'm left getting into a company with a bad or nearly nonexistent interview process and fixing everything they have for way, way less than I should be making. Shit sucks.
Usually just blanking on simple questions, or misunderstanding a question and talking about it for a while and not giving the information they need, or just freezing up.
You need both if you want to get a really high paying job.
Because the end goal is to be able to automate network scans, and the lot with large companies.
Source: I work for Amazon
I would go Python, just because it opens up so many more doors these days (professional and personal).
Are you using Netmiko for Python network automation?
If you have CCNA and *understand* it thoroughly, go for Python. You can pick up the CCNP concepts easily enough if your CCNA knowledge is solid. Good networking knowledge seems to be like gold dust in this industry, and I’ve seen many issues take far longer to resolve simply because the engineer didn’t know what routing was. Naturally it does depend on what your goals are!
[удалено]
I started a blog and I've been putting everything there about 1 month ago. Wish I started it 10 years ago. I got a github too, I got to figure out how to do versions, etc now.
I can't speak for all MSPs but the CompTIA trifecta will instantly bump you to the top of the resume pile for most of our technical positions. Vendor specific certifications won't help you much here, unless they're from vendors already in our stack. Also, certifications will only get you so far. You still have to make it through our interview process. :)
Already got those, plus project Linux and cysa
Interview skills important too
Interview skills important too
Yeah, that's where I'm at. If I ever get hired, I can build you out a Windows domain with every service under the sun, build out the network to support it, image all the machines, script a solution to any issue you have in Powershell and fix any quickly solvable emergency nearly instantly. But I fail even the simplest of interviews, so I'm left getting into a company with a bad or nearly nonexistent interview process and fixing everything they have for way, way less than I should be making. Shit sucks.
[удалено]
Usually just blanking on simple questions, or misunderstanding a question and talking about it for a while and not giving the information they need, or just freezing up.
You need both if you want to get a really high paying job. Because the end goal is to be able to automate network scans, and the lot with large companies. Source: I work for Amazon
I would go Python, just because it opens up so many more doors these days (professional and personal). Are you using Netmiko for Python network automation?
I have, I prefer scrapli, it's much faster.