I'm considering entering the Information Systems Security program at ITT. Would you guys recommend that I get an Associates in Networking OR Programming? Thanks!
Printable View
I'm considering entering the Information Systems Security program at ITT. Would you guys recommend that I get an Associates in Networking OR Programming? Thanks!
My uncle is a network admin and he went to ITT tech but hes says sometimes his job can be stressful but he also says hes the type who likes challenges.
Valor,
It depends on what area interests you more...I would try to learn both, however mostly likely than not, you will end up working mostly in one area (either Networking or programming)
Cheers
:)
P.S.
Just my opinion, netwoking is alot easier to master than programming. Anyone can learn networking, however not anyone can write "good" code. Programming to me is like an art.
It's something that's innate that certain people possess. An analogy of learning programming I like to use with my students is:
"Anyone can go to school to learn art or learn how to draw, however not everyone can become a Picasso."
My thinking on the subject is that during the beginning of the Information Systems Security program, a lot of the networking will be reviewed. I already have a fairly good grasp of networking concepts, and was thinking I could catch up fairly easy. Plus, in order to teach the majority of the ISS program, more emphasis would have to be put on networking, making sure the students understand it.
I'm not as strong in programming as I am in networking, which is why I was leaning towards taking the Programming classes. I was talking to a student in the ISS program yesterday, and he said that there were 8 people in the program that had an Associates in networking, and only one who had his Associates in programming. The programming student was slowly catching up with the rest of the students within the first 2 quarters. I'm not sure of the programmer's previous skill in networking, but after the 2 quarters, he is almost on the same level as the Networking people, due to the amount of networking information being taught at the beginning of the program. Now the programming student will be on par with the networking students, and have all of his programming skill. Does this sound like the way to go, or the Networking route?
I would always recommend that you go with the programming option. That will gives you more opportunities in the work force in my opinion. I have friends who have already graduated college with a Computer Science degree which only included 1 networking class a couple of them are network admins.
I think with the networking degree you will just be able to get an IT job, however, with a programming degree I think you could do either because I dont know anyone who is a good programmer that doesnt know anything about networks also.
Just my two cents. :cool:
Valor
It sounds like what you are describing from the feedback you received from your friends is that taking the programming route gives you the skills/training in networking and an associates in programming all at same time.
Again, really what you have to decide on is what you think your area of interest is? or better yet, what area do you see yourself working in the professional world.. Because I could tell you this, programmers/app developers do nothing but programming and the "network guys" do nothing but design/implement/support and troubleshoot the network/infrastructure.
As a matter of fact, these 2 groups are constantly "butting" heads whenever there's a problem. Programmers blame the problem on the network and the network engineers blame the problem on the software/application....And either group knows anything about the other.
So, In summary,
Choose the area that you see suits you best or think you may have more interest in and it always helps to know a little about the other..It'll make your life awhole lot simpler in the corporate professional environment.
cheers.
:)
N1ghtStalker's
programming has been around for alot longer than "networking" it is just recently that colleges are offering degrees in networking.
"Networking has really only boomed with the introduction of the Internet to the public sector during early 90s...Therefore it took a while for colleges to creat curriculums in networking..
HoweverI personally I agree with you that programmers are very bright and are adaptable to learn anything new...
Aslo, although programmers are very bright individuals, I know alottttttttttttt of programers who know very little about networking,,,( and this is not due to their lack of understanding it) it is just that it is sooooo difficult to know everything..Networking is very very broad. It is not just your simple LAN and IP nodes...
This is not true for everyone. I'm sure it does happen in some companies, but in others there can and will be networking/sysadmin people who have written and do know how to code.....as well as programmers who know about and may have done sys admin/net admin duties. Sometimes they even work well together and complement each others skills.Quote:
Originally posted here by gunit0072003
Valor
Again, really what you have to decide on is what you think your area of interest is? or better yet, what area do you see yourself working in the professional world.. Because I could tell you this, programmers/app developers do nothing but programming and the "network guys" do nothing but design/implement/support and troubleshoot the network/infrastructure.
As a matter of fact, these 2 groups are constantly "butting" heads whenever there's a problem. Programmers blame the problem on the network and the network engineers blame the problem on the software/application....And either group knows anything about the other.
cheers.
:)
I'd recommend checking out both areas and finding what you like best. Opinions are rampant, and none of them will help you be happy. You need to find what you like to do and decide yourself.
I'd suggest you get a well rounded education of both areas since that will make you more useful than someone who has only studied one. It will also open up the most opportunity. If you are a dev who understands networking and system administration you are more likely to develop solutions that take advantage of all the options available to you than someone who is ignorant of those tasks. If you are a sys/net admin who understands code you will be able to write solutions to your own problems and be able to automate tasks to make your life easier. With a knowledge of both you will also be able to better work with 'the other side' making you more valuable, and everyone a little happier in the end.
Take some time, get a couple of cheap boxes and a home networking kit. Build your own setup and see how you feel about it. Grab some free compilers and a couple of good books (pm me for suggestions if you like....) and write some code....see how you like that. It's better to waste $300 on a test environment that will help you make a decision sooner and that you will be able to use for practice for class work than to waste $7,000 and find out you do not like the type of work.
Juridian ,
I think everyone, includng myself, uses the term "networking" so loosly today that they forget that it encompesses a wide range of sub specialties within itself...
A network quote unquote person, can work in one of the following areas of specialties:
1) Network Operations
2) Data Communications
3) Network Implementation
4) Network Design/architecture (LAN/WAN infrastructure)
5) LAN administration
6) Network Management
7) Network Security
Of all these,the only ones I see you need a combination of both skills (and also not always the case) are 5,6, and 7.
Cheers.
It all depends on what you do, and for who.
Im structly speaking working for multimillion dollar fortune500 companys...
Again, depends on who and what. In general, yes there is a separation at alot of companies. But that is not always true....and does not change the fact that programmers with an in depth knowledge of networking are needed in some areas. One such area is developing tools used by networking and network security professionals. There are others as well. I believe it is best to say that in your experience, it is that way. In my experience, there are exceptions and to even promote a division is silly. It isn't incredibly difficult to get an understanding of:
1) Network Operations
2) Data Communications
3) Network Implementation
4) Network Design/architecture (LAN/WAN infrastructure)
5) LAN administration
6) Network Management
7) Network Security
While you will usually not need an in depth knowledge of the configuration of a cisco router, or how to correctly configure a windows 2k dns server (or bind), an understanding of it all from at least the network+ level will help you alot. An understanding of network communications, name resolution, and firewalls can help you figure out why your application (regular app, web app, web service) does not work correctly in your environment. An understanding of system and network security principles can help you set up your development and test environment correctly if you have to do it yourself (which is often the case in my experience). It can also help you when setting up the security for your application for everything from the way it interacts with the firewall to the user authentication methods.
As for design/architecture/implementation....will your application work with a clustered sql server? Web servers behind a bigIP box? Will the web applications talk to an application server? How will all of this react using the technologies chosen, the current code architecture proposed, and the protocols involved?
In a smaller team or one off project the dev may be the person setting up that initial proof of concept environment.
It all depends.
Well, I do really want to study both areas, but I was trying to decide which would look better as a degree. Once I get the Associates degree, which I'm still leaning towards Programming, I will continue and get a Bachlelor's in Information Systems Security, which is definitely my ultimate goal. The core curriculum for the ISS degree consists of the following classes, all 4 credits each:
Internetworking Infrastructure and Operations
Information Security Essentials
Software Project Management Essentials
Security Architecture of Common IT Platforms
IS Risk Management and Intrusion Detection
Fundamentals of Network Security, Firewalls and VPNs
Hacker Techniques, Tools and Incident Handling
Information Security Perspective on Intranet, Internet and E-Commerce Infrastructure
Security Policies and Implementation Issues
Auditing E-Commerce Systems and IT Infrastructure
User Authentication Systems and Role-Based Security
System Forensics Investigation and Response
Securing Windows Platforms and Applications
Securing Linux Platforms and Applications
Legal and Security Issues
and finally, the Capstone Project, which involves a demonstration of the information studied in the core program courses. The assigned project contains a typical scenario involving setting up and securing both intranet and Internet/e-commerce systems for an organization. Students may choose an individual or team project to develop and implement an enterprise wide IS Security Policy and Plan. Students will also audit the project of another student or team.
Thanks for any input guys. :)
Juridian ,
No one is disagreeing with the fact that knowing both is more beneficial than knowing one over the other.
Again the term "networking" is used loosley..Your example of setting up a small LAN is not a good depiction of different areas /skills needed to entering the vast arena of networking.
"Take some time, get a couple of cheap boxes and a home networking kit. Build your own setup and see how you feel about it. Grab some free compilers and a couple of good books (pm me for suggestions if you like....) and write some code....see how you like that. It's better to waste $300 on a test environment that will help you make a decision sooner and that you will be able to use for practice for class work than to waste $7,000 and find out you do not like the type of work."
Let's be honest here, There is sooo much technology out there and soo many areas of specialties that as a beginner, it is best to know which route you want to take from the beginning so it doesn't become overwelming and eventually intimidate the individual.
Just take for example working strictly with WAN technologies, you have:
1)ATM
2)Frame-Relay
3) X.25
4)IP, IPX,Appletalk,DecNet,
5) Various routing protocols, and not just supporting 10, 20 or even 100 nodes, more like
2500+ routers using sophisticated complex routing protocols as BGP4, IS-IS,and OSPF
6)DWDM
7)SONET
8)Voice over IP
9)Multicast routing and QoS
10) and on and on and on,,,,,,,
Ive only touched on Wide area network technologies and in all, you do not need to understand how software is coded in order to excell in area,,,
I didnt want to turn this into a pissing contest but the point here is, an individual should first understand what areas of specialties exist out there that employers are looking for that require:
1)strictly programming /coding skills
2) strictly designing/implementing/supporting and troublshooting network skills
or other areas as you have mentioned where
3) Doing a little of both..
Once a student understands the Job market and the demand that exist out there, the time/resources/money/ needed to aquire such skills and the salary structure for the various positions, then, I believe it makes it much easier to make a decision on what route to take....
Cheers.
I think our problem exists in the way we are reading each others points...
In the end I believe we are both saying that you (Valor) should explore your options as much as possible. Look at the different areas and specializations of both, the job market, explore the technologies a little on your own, etc so you can make a more informed decision.
Both programs at ITT teach a little bit of the other anyways so if you decide that you want to switch at any time a portion of the classes will transfer so it won't be a total loss.
well said !!
It really does'nt matter what you study in college, the thing about college is that you will learn more about theory than actual practical knowledge. If you like writing code then that may be the way to go, but I should tell you that all the good coders I know never took a college class, for the most part, they were self taught. So unless you LIKE writing code I would'nt go that way. Networking is really the same way, it is a mostly self-taught skill as well.
I can learn more by sitting in front of my box for a week than I ever learned in a semester of classroom instruction. I know you have heard this answer form most everyone that responded to your post, but it really comes down to what you enjoy the most. Don't worry about what kind of degree is going to "look" the best because ultimatly it won't matter.
Chances are your first job will be sitting at help desk anyway, and in the IT field, experience matters more than degrees.
Good luck with whatever avenue you decide.
If you all don't mind me putting my two cents in, as a Technical recruiter (Network Engineer/Architect in my former life), I would definitely recommend the programming, even if it's in addition to the Network skills. Over the last two years, I've noticed allot more positions termed "Network/Systems Engineer/Admin" with more advanced programming skills. I'll agree with Juridian's statement that [gloworange]"I'd suggest you get a well rounded education of both areas since that will make you more useful than someone who has only studied one."[/gloworange] Companies are looking for "multifaceted" people, who have crossed over to other disciplines of the IT industry.
Yeah, I think my knowledge of networking is quite sufficient, but it's all self taught. Later on in the program I'll have some 'formal' training. I've pretty much decided to go with programming though, as I think it will complement the security skills nicely, and companies will hopefully greatly accept the "multifaceted" package of skill I can bring to them. :) Thanks a bunch guys!
I found this Q1/Q2 2001 (I know, I know, It's 2 years old) Market Snapshot that does a salary range comparison for Tech related jobs. I don't know if these salaries are still pertinent but I figured maybe it could give you a glimpse into some idea of the salary market. Check it out if you think it will help you in your decision making process. Good Luck.
Tech Salary Comparison 2001
With a networknig and communications management degree from Devry University, you are eligible for all of those positions you listed gunit.
I am going to go to devry and work towards this degree for a number of reasons.
Devry is one of the leading schools in the IT industry.
You are always using new technology so you will be able to stay current.
With the degree that I will be receiving, I will have so many opportuinities in the IT field.\
I think it all depends on what you are wanting to do with your life.
If you are wanting to mainly be a network admin/security admin or anything else in that field then I would suggest that networking would be the most important. Then after you get your networking classes out of the way, come back later and learn some programming.
A quick note on the "salary range comparison" charts and stats that are out there, take them with a "grain of salt". One of the reasons is that although they give you the low to high salary average, they don't tell you how long the "employee" has been in the company, what size or type of corporation it is, and so on. There are alot of other factors that aren't shown.