Discussion Locked

What would you look for in an IS/IT undergraduate program?

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

TechRepublic is gathering information about IS/IT undergraduate college programs, and we'd like to hear from you.

If you were looking at IS/IT undergraduate college programs, what criteria would be most important to you? Curriculum? Facilities (for instance, how cutting edge is the computer lab)? Faculty? Other?

If you have an IS/IT degree, would you recommend your college's program to someone else? Do you think your IS/IT degree helped you get hired or promoted?

Thank you in advance,
Mary Weilage, TechRepublic

6 replies

by justin james

Good questions! Personally, I think that cirriculum and faculty are the most important. Facilities is totally unimportant... anything you need to do (in terms of getting a BA/BS, at the very least) can easily be done on a 3, 4 year old computer and network. You're learning principles and concepts, not re-writing a graphics rendering engine, after all.

I've taken a look at a lot of CS programs. Many of them are simply *too* hands-on, they don't teach you the underlying principles, they just shove a compiler in front of you and teach you "shake 'n bake" programming. Other programs simply teach you far too much theory, and treat programming like this ivory tower, academic subject; the people who come out of those programs need a lot of time to adjust to "the real world". So I'd be definitely looking for a cirruculum that has enough "hands on" to teach real-world skills and keep me engaged, while having enough theory to be more than a "shake -n bake" course.

The faculty is important too. They need to have real-world experience. I would not be looking for a "big name" professor, just professors who have been in "the real world" as well as being experienced teachers.

The way I would evaluate such a course would be to look at the cirriculum, read as many of the syllabi as I could, and try to glance through a few of the textbooks (if available somewhere for free) to get a feel for what the work would be like. I'd also visit the professor's Web sites to see the class notes. If possible, I would sit in on a few of the "Intro to..." classes to get a feel for the quality of the teaching staff in person.

finally, don't forget the overall school itself. Would you feel comfortable going to school with its culture and attitudes? Is it in the country and you want to be in the city? Are you really studious, but the sidewalks are covered in empty beer cans and vomit and it is Tuesday morning? Do they have clubs and activities that you would be interested in participating in? If you are in a great program at a school you hate, you'll be miserable. I lucked out, I loved my school but hated my CS program... changing majors was easier than changing schools! I ended up getting a top-rate education in the liberal arts, and enjoyed myself immensely. Better to finish with a non-CS degree than be strapped with debt from a degree you don't even finish.

Remember, this is an *investment* that will cost you up to $25,000 per YEAR for a minimum of FOUR YEARS. On top of that, it will directly affect your life significantly for at least a decade (the "career shaping shelf life" of a CS degree in most areas of the IT industry... but those early jobs shape your later career too!). Getting a good education (especially at a lower priced school) can literally pay for itself in a few years, and then be pure profit, especially for an entry-level programmer. For something of this magnitude, you'd do your research and spend some time at it.

J.Ja

by the 'g-man.'

Industry placement for 6 months to 1 year. That way when you finish the course you actaully have some experience to call on when going for that first job. Sometimes you even end up where you were placed.

by justin james

When I was in college, I started my career my sophomore year. I worked at the help desk for the computer labs, then did a few Webmaster gigs part time. I also did a summer job with a big company. By the time I graduated college, I had gotten the "entry level" stuff out of the way, and I was considered "mid-career". Not only did those jobs pay better than flipping burgers, but they gave me a good idea of some of the possibilities in the IT industry, as well as some good references. Comparing my salary within 12 months of graduation to that of a lot of other people I know, it reaped huge rewards.

J.Ja

by charliespencer

Among the other factors mentioned, I toss in an active chapter in a one of the national professional IT organizations.

by notsochiguy

Some of the factors that influenced by decision (both under, which wasn't IT, and post grad, which is) were:

Curriculum (did the core classes fit well with my desired career/educational outcomes, do they have a wide depth and breadth of program choices in a broader field, or are you limited to only a couple of possibilities)

Faculty (are these just talking heads, or do they have real experience/expertise in the subject matter)

Reputation (will a degree from XYZ carry 'name recognition value', does it have a large/influential enough alumni base that I could parlay into networking opportunities)

Cost (does spending $20000 per year at option one make more sense than spending $14000 at option two, considering the other factors listed)

My undergrad actually isn't in IT, so I can't speak to whether or not it helped, asides from passing initial HR filters (yes). However, my Master's program did help me land my current position, as well as opened up some lines of communication with others in the field; so there does seem to be a definite benefit (and I'm not yet finished).

Speaking of promotions in particular, a couple of my former employers had a strict ceiling on how far someone could advance without a certain level of education. Without an undergrad, you couldn't make it past Supervisor (which was a step below Manager, and above Front Line Lead). Without a post-grad, you couldn't make it to VP (Director was as far as you could go). The titles at both places were slightly different, but the example is relatively accurate.

Personally, I think that is an exceptionally limiting policy (as I'm sure Gates, Ellison, Jobs, Dell, et al would agree). Just offering it up for a point of consideration.

by jmgarvin

A) Member of the ACM and/or IEEE
B) At least one year of programming courses with lab work
C) Operating Systems, System Programming, and Architecture flavored courses listed in the course catalog
D) Partnership or at least working with the government or industry in a few research or practical projects

I am going to a school (beware, plug ahead) New Mexico Tech that works with Los Alamos National Labs, Sandia, and various corporate sponsors and interest in various project. I find this helps the undergrad program become more focuses on producing "out of the box" graduates that are ready to take on projects.

This discussion is closed to new replies.