Any IT Guys Here? Trying to Get Into the IT World - Advice / Suggestions / Stories?

[BrianSD_42]

Any interest in learning Python?

I am currently learning Python in my spare time using this website: Table of Contents ? How to Think like a Computer Scientist: Interactive Edition

http://interactivepython.org

It is a completely free interactive website created by several CS professors. Pretty cool actually for going from basic/beginner to better than that, tracks your progress and everything.

Anyone else doing self paced tutorials? Suggestions?

 

[hawkmanjr]

Any interest in learning Python?

I am currently learning Python in my spare time using this website: Table of Contents ? How to Think like a Computer Scientist: Interactive Edition

http://interactivepython.org

It is a completely free interactive website created by several CS professors. Pretty cool actually for going from basic/beginner to better than that, tracks your progress and everything.

Anyone else doing self paced tutorials? Suggestions?

I did Codeacademy's course and am now reading Automate the Boring Stuff with Python. The Codeacademy course was free and neat because it actually graded your code. I'd be interested to hear others' comments about good literature or guides online!

 

[Koko4]

I did Codeacademy's course and am now reading Automate the Boring Stuff with Python. The Codeacademy course was free and neat because it actually graded your code. I'd be interested to hear others' comments about good literature or guides online!

Before I started school, I was learning JavaScript with Treehouse. I actually preferred it (a LOT) over CodeAcademy, even though it wasn't free. My problem with CodeAcademy is that there are multiple ways to handle some of these problems, and your code should be graded on whether or not it produces the right output. CodeAcademy, at least for me, was too demanding with what code "style" they wanted you to follow. Your code could work, but if it didn't match exactly what they had as correct, it would be marked as wrong.

When you get into more complex concepts, I think that you tend to develop your own style and it's more about getting the program to do what you want it to do, than it is doing it with the exact syntax and structure that the author of the course used.

Of course, there are exceptions, like when your code is unnecessarily long or sloppy.

I paused my subscription ($25/mo) with Treehouse when I started school, since in school they use Java. I might look into it and see if they do offer Java and use it as a supplement to what I'm learning now.

I've tried not to confuse myself at this point by learning a little of a variety of different languages; rather I am trying to get as proficient as possible with Java and then I can start to learn other syntaxes. The idea behind coding remains the same, and then the syntax just changes.

 

[T4R2014]

Focus less on the Enterprise IT and more Software Development track. These are two VERY VERY different things from a jobs perspective.

:car:

This is such a great point that is often not stated very clearly. I see plenty of CS graduates starting out in IT helpdesk jobs. Some people may say it's a start to a career, but I honestly don't see these IT jobs being relevant to a CS degree which already requires classes in algorithms and coding. As a matter of fact, most people I've seen in these IT fields did not even have a CS degree. Most had certifications coupled with an unrelated degree in some cases. You aren't using a CS degree to its fullest potential if you don't intend to take on a developmental role.

I'm a recent CS bachelor's graduate. Going back to school next week for a Master's in Cybersecurity. My personal opinion on schools is that the name matters a lot. You may save some money by going to a smaller school, but is it worth the savings? Of course, there's plenty of people doing fantastic with a degree from a smaller name school, but I think that personal connections may play a big role in this. Why do I think this? I went to a smaller school and realized these downsides afterwards. Cost and distance was of great importance when I was applying in high school, but I learned pros and cons along the way. Now, I'm after a MS degree from a bigger name.

Feel free to chime in on what I've said. I enjoy these kinds of discussions and I feel like there's so many unknown unknowns when it comes to careers. Much better than the d!ck waving matches in the threads running a fine line with politics.

 

[AntleredRuin]

I'm probably gonna step on some toes with my opinion, but here goes.

I don't have near as much experience as some other people who have posted on here (about 8 years) but in my opinion, if you're looking to get into general IT (like helpdesk support), then DON'T go to school. You won't learn much of anything there that you can't figure out quickly for yourself, and you'll waste a lot of money in the process.
Stick with the CompTIA certs, and get a couple years experience under your belt. Then, use that experience to work your way up to bigger and better things.
Once you have a couple years under the basic HelpDesk scheme, start looking into working for a MSP (Managed Services Provider). Pretty much, these are companies that contract themselves out as IT guys for other companies. You'll work with a team (usually not too big), so you'll have help strengthening your weak areas without having to reply on internet forums too much.

You'll get a lot of experience with ALL SORTS of environments.
The MSP I work for works mainly in the medical field (dentists and opticians), but we also work with clients in advertising and manufacturing. Hell, we manage the CC Cameras for the underground tram at the Bush Intercontinental Airport in Houston. So I'm all over the city, and I'm never bored.

To the people who say that IT guys never get time off; that's not true. You just have to have standards that you will stand up for about what's expected of you. I do work some overtime; that is inevitable. But on average, I work less than 50 hours a week, usually less than 45.
We have rotating on-call weeks, and the on-call guy keeps his phone on him on the weekends and after hours, just in case, but any real work is rare.

Working overtime is usually a result of poor planning on someone's behalf. If your boss gives you a project after hours, then let him know that you'll take care of it when you get into work the next day. If he insists, reassess how important this particular job is to you.
If a client calls or e-mails, see how urgent it is, and let him know that if you address it now, there will be an extra after-hours fee, versus you handling it at 8 the next morning.

I work hourly, and would not have it any other way in this industry. When I work overtime, I make time and a half. I work set hours (plus a bit of overtime), but I'm in charge of arranging my own schedule (maintain communication with my team, of course) so as to not waste time. I do random overtime projects a few time a year (software upgrade, etc) and I can expect a nice hefty bonus in my next paycheck, because of the overtime. We just did an O365 migration for a client a few weeks back, where I remotely worked off and on over the weekend (and still had time to spend with my wife), and I made nearly $1000 extra because of this.


When you're interviewing for a job, the hiring manager should tell you what's expected. He'll tell you how you're paid and what hours are expected of you. I agree, if the pay is salary, with random overtime, think long and hard about accepting. If the pay is hourly with more or less set hours, you're probably pretty safe. He won't force too much overtime on you, because he won't want to pay you more.

That's not to say that you can't make good money with an MSP. I have consistently maintained my own personal goal for the past 4 years that I've been here, and that is to make at least $1/hr more than my age. I'm currently making $3.5/hr more, so it's going great.