bane said:
I realized that if I ever leave the state (which is likely at some point considering my career options are stronger in WA) it would be better to come from a recognizable school. All the others in the state, except BYU, just don't have that sort of clout. Well, Westminster does a bit but their CS program to my understanding just doesn't compare to the U's program.
I don't think you need to be concerned about that.
I've been a professional software developer for nearly 20 years now, and in much of that time hiring decisions have been part of my job. I've also had lots of opportunities to be on the job candidate's side of the table (as a consultant, I effectively get a new job every few months, and as an architect/team lead I end up hiring a new team every few months).
In this field, degrees matter very little, and choice of school is almost completely irrelevant. What gets you jobs is your experience first and foremost, interviewing skills second and degree is a very, very distant third and even then it's more of a yes/no question. No one after your first job is going to care about evaluating the quality of your degree.
The catch, as always, is how you get that first job so you can start building a resume, and of course a degree is a much greater consideration there. If you graduate from WSU, for example, you'll have a much harder time getting that first job with a big corporation than if your degree is from the UofU or, even better, a really big-name school like Stanford, MIT, CMU, or CalTech. But there will be plenty of small companies who are glad to exploit you for peanuts no matter where your degree is from.
Assuming you're bright, talented and motivated by a love of the work, you'll quickly end up in a decent job no matter where you start, so the only difference your choice of school will really make is how much money you can pull down in the first year of employment. And even that isn't true if you can manage to acquire some solid experience before graduating. I highly recommend trying to get some part time work while still in school, or, perhaps even better, write some open source software. When I'm hiring people fresh out of school, a good open source project on the resume is extremely compelling, plus it also gives me an easy way to evaluate their ability.
My advice to CS students is to choose their school based on where they'll get the best education, not what will look best on their resume. The environment that will give you the best education is different from person to person. In my case, what worked for me was a mediocre program that gave me a key to a lab full of millions of dollars of equipment so that I could go through a serious
larval stage where I worked with lots of high-powered professors -- none of whom taught at the school I was attending (WSU).
The CS world has changed dramatically, however, and unless you want to focus on massive parallelism or similar niches (though that one is growing rapidly -- even my laptop has two cores these days) access to equipment isn't the issue. Nowadays, I'd focus on finding a program that is very heavy on both classroom theory and on practical student projects. The theory is crucial for long-term survival in an industry where you get a completely different toolset every couple of years. A bone-deep understanding of algorithms, data structures, modeling and data communications theory will work for you whatever tools you're using, whereas deep skill in the current hot language will be obsolete in a few years. The practical student projects are essential because they teach you a lot of the issues you'll face in the real world in a less stressful environment.
Honestly, though, if you're motivated enough you'll self-educate on whatever pieces your school's program doesn't cover, so what you really need to do is focus on finding a way to get some experience.
Come to think of it, if you know any PHP, or want to learn it, I might have a job for you. PM me if you're interested.