Career in Programming vs. Networking

AI Thread Summary
A career in programming offers diverse opportunities, especially in gaming, but can involve long hours in a relaxed environment or more flexible hours in corporate settings. Networking careers may require more effort to achieve higher-level positions, focusing on security and network design, but often start with less skilled roles. A Computer Science degree is generally recommended for both fields, with programming being more engaging for those who enjoy creative projects. Motivation and personal projects are crucial for learning programming languages effectively. Ultimately, choosing a path should align with personal interests and long-term career goals.
JC92
Messages
10
Reaction score
0
Ok, so apart from my desire to become a Physicist or Engineer I've also considered going into a more computer related career in either networking or programming. Yea, let's face it I haven't really been able to decide. One way or the other I'd like to be prepared or at least know what I'm getting into. I've spoken to people about both programming and networking, but I still don't really have a good idea of what a career in either field would entail. As far as I know a degree in Computer Science would be the best choice to start off. However, after that I'm clueless as to what happens. So basically, I would appreciate some general information on the types of jobs you start out with for both careers, what is the process for getting certifications in networking/learning new languages for programming, and what is the normal work day like? Also one other note is that I would really like to be able to program for a gaming company, however I don't know how difficult it would be to land a job working for one. Thanks in advance for any responses.
 
Technology news on Phys.org
I've been a programmer for the last 11 years, doing the run-of-the-mill corporate grind. Here's my insight:

Your happiness in programming probably depends on the job environment. If you're working for a gaming company, I've been told to expect to work long, hard hours, but in a laid back environment. That is, the people are friendly, nice, generally young, and do fun stuff together, even at work.

If you work for a big company, your hours will probably be pretty flexible, and you won't be expected to work all that hard. There's enough bureaucracy to give you a steady, but uninteresting job. You may or may not need to be called for support at 4am, but probably not.

If you're at a small company, you'll be the go-to-guy for everything. You know programming? That means you know everything else, and can do everything. You'll feel very useful, and do a wide enough variety of things to keep interested. But you'll also likely be the go-to-guy at 4am when there's a problem.

Obviously, that's some massive generalization-- there are always exceptions.

For me, programming is made more fun by writing more tangible things-- desktop applications, web pages-- stuff like that. Doing more obscure things like writing a linker for code compilation, or writing data analysis code, or whatever, isn't as fun, because it's less "hands-on". You won't find much use for it in your everyday life, unlike writing web pages, where you can use your on-the-job skills to also do fun personal projects.

Networking? I haven't has much experience with it. I haven't been overly impressed with my company's networking group, but that seems to be because we either get "the incompetent guy", or we get they guy that's ALWAYS too busy. And from what I've seen, they're VERY frequently on call, and called into work weekends, because that's the only time of day when people aren't using the network, and makes it the only time that changes can be made.

So my vote is for programming. But there are a lot of variables involved.

DaveE
 
I used to be a software engineer until i became disabled. The VA is sending me for a degree and computer network security is one of my majors.

Okay. First, it is all on what you really enjoy doing.

Programming is great if you love to do it. And you can have a constant search for new things. It is all on you. The nice thing about it is that technology changes so much, that every few years you can jump in and quickly build a desirable skill set.

The key is that you have to love it, and always challenge yourself, even if your job is doing the same old thing.

Anymore you really should have a comp sci degree. Companies shy away from the self starters.

The network side a bit more complicated. I agree with Davee, most networking people in companies are not very skilled. They took a few courses and maybe got a certfication, but they other than that they are nothing more than pc assemblers who connect cable. And they know how roaming profiles work.

That is not the networking you want to do, but sadly most of the jobs are in this area.

The higher end networking is designing and implementing networks, security, and desiging the server architecture is where you want to be. But you have to build your credentials, and you will probably have to work for a consulting firm and travel.

The focus now is security, which is beyond users permissions. It is a very dynamic field and you need to build a wide range of experience beyond one operating system or network technology. There is a certification for it and it is the fastest growing technology field right now.

I am going into with a lot of technical knowledge, but I am not a nuts and bolts network person.

If you really want to feel yourself out with the networking. Cisco ( I am not a big fan of their books ), has a lot of free resources online, and buy one of their books for the CCNA certification. ( this is one you should have ). See if you like it and if it interests you.

Programming will get you a better job in the short run, but if you really go into the higher end networking you will do just as well. ( it will take you a few years to get the credientials and the experience ).

Good Luck.

Personally I would urge you to go programming if you like it. But there is a career path in networking if you really find it interesting. ( though it will take more work and determination on your part )
 
Thanks for the responses so far. Programming definitely sounds more interesting on a whole. The only problem is that I've never really had the motivation to teach myself a language. I was going to take the C++ class we have here at my high school this year, but sadly not enough people signed up for it.

I actually at one point tried to teach myself C+ or C#, something like that, but I had nothing in mind to use the end product for since it was essentially a personal undertaking. So I eventually slacked off and the ebook has since been collecting digital dust in a random folder.

As for networking, I've had even less experience. I mean I've set up my home network and such, but not much else. If I did go into networking it would most likely be in the security aspects of it. The more money long term I guess is a plus, but I would rather enjoy what I'm doing rather than hate it and make more money.
 
JC92 said:
The only problem is that I've never really had the motivation to teach myself a language.

Yeah... that's a real problem.
 
JC92 said:
I actually at one point tried to teach myself C+ or C#, something like that, but I had nothing in mind to use the end product for since it was essentially a personal undertaking.

Yeah, you'll need some pet project ideas to work on. And most importantly of all, the pet projects have to be reasonably bite-sized pieces of coding. Nothing like "write my own version of Halo". More like "write a program to display the Mandelbrot set" or something like that. It's got to be something you can manage, and something that you can achieve within reason.

For me, I wasn't interested in programming until I found graphics. Once I could write programs with graphics, pet projects, games, and other stuff seemed to come up all the time, which I would just have fun writing. Unfortunately, it seems like everyone treats graphics these days as though it were some huge complex process-- probably why I never continued down the C++ path after school-- they never REALLY taught us how to actually write anything graphics-wise!

DaveE
 
CRGreathouse said:
Yeah... that's a real problem.

Well keep in mind that I'm still in high school, and I've never gone about teaching myself something as big as an entire programming language. I'm sure once I find a project to work towards and get that first language down pact I'll be immersed in the subject enough to where learning new ones and finding little projects to help me out won't be too hard anymore.
 
JC92 said:
I'm still in high school, and I've never gone about teaching myself something as big as an entire programming language.

Bah! [gathers crotchety old-man powers] In my day, I started learning BASIC programming when I was in 6th grade! In the snow! Uphill both ways! Huh... actually, I suppose technically, I knew 4 programming languages by the time I graduated high school, although only 1 of those did I learn for fun on my own (BASIC). The others (Logo, Pascal, C), I took classes in before doing them on my own (I did a little Pascal on my own after the class, but not too much).

Anyway, it's not about learning an entire programming language. It's remarkably similar to human languages. You can learn enough French to get by in France, but not know nearly the whole language. And until you have a reason to learn French, you probably won't do much learning. Sitting down with a "teach yourself X" book probably won't work-- you've got to have some goals in mind, or some inspiration that it allows you to achieve. THEN you'll start learning.

DaveE
 
davee123 said:
Bah! [gathers crotchety old-man powers] In my day, I started learning BASIC programming when I was in 6th grade! In the snow! Uphill both ways! Huh... actually, I suppose technically, I knew 4 programming languages by the time I graduated high school, although only 1 of those did I learn for fun on my own (BASIC). The others (Logo, Pascal, C), I took classes in before doing them on my own (I did a little Pascal on my own after the class, but not too much).

DaveE

Yea, I wish I would have had a better choice of classes to take for programming. The only class that I have been able to take is Visual Basic, but our teacher for the class was in the Air Force reserve or w/e and got called back on duty at the beginning of the year. Essentially the entire year we had substitutes coming in and out of the class that didn't have any experience at all with programming. Since then, most of the classes have just been dropped because of the lack of a qualified teacher and not enough people signing up for the class.

I'll probably be going to a community college, for this summer at least, before I head off to a university. I'll have to check, but it's possible that they offer some programming classes. That would give me a chance to take a few good classes.
 
Back
Top