I think it's silly that some places "require a degree" when it seems like anyone can get "a degree" with enough time and money. I know I've sure met my fair of idiots with a degree.
I don't disagree with you, but I don't make the rules unfortunately. The company I work for now is heavily involved with higher education, so I can understand them requiring degrees for just about everyone. But other companies? I don't really understand it. I don't think a network admin with a degree in medieval history is any more valuable than a network admin without that degree.
Also, I wonder if there is a chart somewhere that shows the percentage of people working in the field their degree is in? Then again, most of the stuff I do on a daily basis I would imagine only a small percentage have the mental capacity to comprehend, same as specialist doctors or actuarys.
I don't work in my degree field. In fact, my degree field is far beyond my current job. I have a degree in EE and used to design hardware in grad school. EE >> IT in terms of technical skills, but I just lost interest. Recently, though, I'm starting to gain interest in it again. Maybe I'll pick it up as a hobby.
As far as trouble finding a job, I'm fortunate enough to have never had that problem. I'm in my 4th IT job, only leaving to go to something better. When I went from my 1st to 2nd, it was to cut down on commute time and I had a kid so wanted to be closer to home. No issues getting hired w/ my A+ and experience, plus it was about a 30% pay increase. Two years at 2nd job, I got my MCSE, added it to my resume, was headhunted, got hired on my 3rd job with about a 35% pay increase from my 2nd job. Two years at 3rd job, met some guys through a local HDI chapter, they told me about a position they had open that was less work than what I was doing at higher pay with more opportunities, and while it was only really a 8% pay increase the benefits are much better.
I guess I'm just lucky that I really know my shit and have proven it when required.
YMMV. Every IT job I see posted at my career level requires a degree.
Some people don't like the idea of having to support new OS's when they come out, new drivers, security patches, new software, iterations of backend tools, but I still like doing all that at the age of 32. Hell, I get excited when new software comes in and I get to tweak it and repackage it and send it out.
I work at a place that would be considered leading edge in technology. On one hand, that's good because you get to play with new stuff. On the other hand, it sucks because you often move too fast. In our case, we have everything (email, phone system, fax, etc) so tightly integrated that now, it is a REAL pain to support it all. Office 2010? Great! Oh, wait a minute -- our VOIP plug-ins aren't certified. Oh yeah, and our email archiving plug-ins won't work, either. There goes that plan!
Fortunately, I don't have to deal with it anymore but when I did, it got kind of old. We didn't upgrade for rational, well-thought-out business reasons, and THAT was the problem I had. My last job was at the other end of the extreme -- you had to make your case 10 times before they'd spend a dime. Still, though, I'd say I enjoyed it more, as I was the lead architect on our global Active Directory rollout. That was the best project I've ever worked on in my entire career. You haven't lived until you deploy AD to 40+ major sites around the globe with some having circuits as small as 64K.