Quench24 wrote: » Thanks for the reply Jibtech. To answer your question, I have verified equipment inventory, I have created knowledge base documentation. I hope you understand though, I cannot stand down time, which is why I'm seeing if there ARE any positions out there with little to no down time.
jibtech wrote: » I was at a non-profit for several years in an IT department of two, supporting about 300 users. I did break-fix, web development, system administration, compliance and database administration. It was a good gig, and I learned a lot from it. Might be worth looking into.
Danielm7 wrote: » I started my IT career that way. A bunch of offices and just me, ran around like a nutter a bunch but also got very well rounded experience. You mentioned not really wanting to fill your downtime with studying. Are you working towards any sort of goal outside of just being more busy?
DatabaseHead wrote: » MSP should take care of that. You are usually overworked, but paid well too (in the cases I have seen). Might be something to consider. ***I managed a large service effort for a fortune 500, and while the guys / gals were overworked they were also paid 30% higher than the market median. There was usually 0 downtime and trust me when you get it, you loved it (it was soooo rare). The position was application support, true application support. Reviewing bugs in the code, database review and updates (changes) in some cases. 0 downtime.....
Quench24 wrote: » Goal: To pass the WIN10 MCP Today
Danielm7 wrote: » Great, but super short term. What's your long term career goal? Figure that out and start working towards it in all your free time.
Shane2 wrote: » I'm sorry, but if you are in IT, and are constantly engaged, you are doing something wrong. Downtime should be used to improve you skills. And in that case, it is not downtime. It is being proactive. A job where you are constantly engaged is a recipe for burnout.
Quench24 wrote: » System Administrator. Lately I've been thinking about Web Development though. More engaging probably and less downtime with constant coding.
jibtech wrote: » I want to make a different suggestion. Rather than thinking about specific roles, think about the skillsets you want to apply in the job you want. System Administration can mean a lot of things. I have seen everything from Application Specialists to Network Engineers doing what I would consider system administration. Same goes for web development. Instead of thinking about web development, think about development in general. It doesn't all have to be coding a web page or an application. With the trends in enterprise services bus and master data management, along with the push towards devops, there will be a lot of work for developers for a long time to come. Basically, think bigger, set a target and go knock it out.
jibtech wrote: » I have to admit, I am a bit confused. Are you looking to get into front end, which is primarily design, or are you wanting to get into development which is more focused on code? Both have a lot to offer, but they are definitely not the same thing. If you are wanting to get into front end, start learning HTML5, CSS3, Javascript for starters. Once you have those pretty solid, learn jQuery. It is important, but get a solid foundation on the first three. Start with the basics on W3Schools. Once you have those down to where you can do it with your eyes closed, get a Safari membership at OReilly Press. Start working your way through each of the books on those subjects. As you go build a portfolio of sites you have designed. There is also a lot of work around WordPress. Opinions on WP aside, it is a marketable feather to have in your cap. If you are wanting to get into more development, still start with HTML5, CSS and Javascript. Next, jump into PHP and C#, with some jQuery thrown in with it. Expertise in PHP, C# and jQuery will set you up with a solid base. Personally, I would learn both object oriented PHP, and procedural PHP. Once you have a procedural language down, and you have an object oriented language down, everything else becomes almost trivial to learn. If you want to get more into software development, start with C#. From there expand into C++. If you have a Navla Surface Warfare Center near you, and that is a direction that interests you, look into a language called Ada. An Ada programmer doesn't make a bad living. If you want to get into System Administration, you need to decide on a first platform. Linux or Microsoft. If Linux, pick a distro and use it as your everyday computer. While you are learning it, start looking at a Linux+ cert. It won't be the cert that gets you the job, but if you understand the content well, it will position you well for a Junior Linux Admin job. Linux guys take it serious, so they will expect you to know it. Oh, and decide on vi or emacs. It matters. (The right answer is nano or pico, but the Linux guys won't want to hear that.) If you choose Microsoft system administration, MCSA is your first step. Everything branches from there. Microsoft Virtual Academy is a pretty great resource. If you are more into network engineering, start saving your pennies and build a small lab of Cisco gear. Start with the CCENT/CCNA track and build from there. If you are more interested in Cybersecurity/Information Assurance, go download a copy of Kali Linux. Go through the tutorials at kali.org and master them. Then start playing. If you want to do it as a career, Security+ is your first stop, working up to your CISSP. There are others as well, but by that point you will have a better idea of what is more valuable to you. IF you want to be the baddest Leroy Brown on the block, OSCP is the place to start. It is a 24 hour effort in which you have to get root. It doesn't get much more real than that, and the OSCP is well respected. Save the CISM for later down the road. If you are more interested in compliance, start again with the Security+, followed by either the CISRCP or CISA. CISA would be my preference. That is as thorough an answer I can give right now, on how to get started in the broad categories of IT. There are always niches, and working your way through one of the above will help point out those niches to you. All of the above are going to require solid effort and studying. You will never stop studying in the IT career field. This is where the downtime helps. Bootcamps are fun as a refresher, right before a big test. I did it for my MCSE back in 2006, at Todd Lammle's facility. (Lost opportunity, I know.) But, I wasn't trying to learn it cold. Bootcamp are exam prep. They are not training.
jibtech wrote: » Which exam was it? MCP is an automatic designation when you pass any of the qualifying (non-MTA?) exams.
Quench24 wrote: » What is MSP? I don't have much experience with coding..