Im sure many of you had the choice of being a programmer or doing IT. How did you come to the conclusion of one over another. I know its not a real question, but many of you seem the best to answer such a question.

I need to decide on which round I will go down and am having trouble making such a decision.

link|improve this question
3  
This should be Community Wiki – Izzy Oct 31 '09 at 18:19
Yes, definitely wiki – squillman Oct 31 '09 at 18:24
3  
Edit the question and there is a CW checkbox underneath the question box – squillman Oct 31 '09 at 18:33
2  
Per the <a href="serverfault.com/faq"faq</a>; "Avoid asking questions that are subjective, argumentative, or require extended discussion. This is not a discussion board, this is a place for questions that can be answered!" – Brian De Smet Oct 31 '09 at 19:17
1  
Since when has being a programmer not been an IT job? Did I miss a memo? – womble Nov 1 '09 at 11:47
show 3 more comments
feedback

5 Answers

up vote 1 down vote accepted

Programming is just a part of I.T. To me it's more like, "Why did you decide to get a Computer Science degree instead of an Information Systems degree?" There's more creativity to build stuff in programming than say, network administration. The network admins do build servers, VMs, the actual network, and things like that, but a lot of their time seems to be administration of the system. Whichever one you decide, you should know at least some about the other one. Both require critical thinking skills for troubleshooting, but in different ways.

For me it was decided when I was about 13 and banging out BASIC apps from books. Ever since then I had a fascination with computer programming and it stuck with me. I just don't have that same fascination with other I.T. jobs.

link|improve this answer
feedback

I started out programming and then decided I didn't like typing line after line of code and to be honest, the deeper I got the more I realized I didn't have the talent for programming.

link|improve this answer
feedback

I started out in IT, spent 8.5 years there, then found that all of the stuff that I liked doing the most involved scripting and writing applets and tools to make my IT life easier. I got the opportunity to move into a dev group in a split IT/dev role and love it. Through college I couldn't imagine being a developer (thought I'd hate it) and was interested in mainly networking and system admin. Now, I love doing both. Fortunately for me I can do both, so my decision to be in IT at first turned into a decision to do both.

link|improve this answer
feedback

A surprising number of people tend to almost "fall into" the role. You start out as one, opportunities come up or circumstances change, and you end up as the other.

My advice is that you're more likely to find a job doing something that you're good at, and more likely to get personal satisfaction from doing something that you enjoy. Only you can make that decision.

Remember though that it's not final. You can switch, and skills learned in the one can give you an advantage in the other.

link|improve this answer
You can always switch later. I know a few people who just "fell into" programming. One was an MBA who wrote so much Excel VBA, and go so good at it, that he changed over to being a programmer full time. I know another person who was asked to try this, or learn that, and on her own she came up to speed and transitioned into a full time programming job, no C.S. degree background, just lots of good OJT and a strong self learner. – Bratch Nov 1 '09 at 17:23
feedback

Nobody can decide these things for you. We each have our own set of circumstances and therefore our own reasons for making our decision. Your circumstances will be different. It's your life, your decision. If you later find you made the wrong one just switch. It's not as if you're locked in for life. Just bear in mind that few employers want someone who is indecisive.

link|improve this answer
feedback

Your Answer

 
or
required, but never shown

Not the answer you're looking for? Browse other questions tagged or ask your own question.