My experience is in line with the author's. Finding a job has always been relatively easy (beginning at a certain point, which I will elaborate on) and I do not have a degree of any kind. It's my opinion that three factors are primarily responsible for my state of affairs.
1. I started working at a local ISP when I was 15 years old. This was around the time that 28.8kbps modems were all the rage. While I was very green I had unbounded enthusiasm and desire to learn whatever I could about technology. The ISP got a super cheap tech support person and I got paid to learn. After a year I got a chance to do UNIX sysadmin work, and my level of experience began to snowball.
The (fairly obvious) takeaway here is that I built experience. Businesses don't want to train you if they can help it. Not able to find a learn-on-the-job opportunity? Take the author's advice and contribute to an interesting open source project.
2. Befriending an employee of one of the largest ISPs in the United States ended up landing me a development position on a pretty large contract. I worked damn hard, and ended up contributing in a fairly visible way. Because the job was for a company in the Fortune 50 I've since been able to point to it as social proof that I at least have a vague idea of what I'm doing. Employers love this. This is when job hunting became dramatically easier.
You may think the takeaway here is to be lucky, but I disagree. The takeaway is to get to know people that you can develop mutually beneficial relationships with. To this day I still get contract work and referrals from people I worked with on that one job.
3. Location. Companies will sometimes relocate you, but I've never seen one that will do it without there being a very compelling reason to have you on staff (ie, experience and a proven track record). You have to go where the jobs are. Sometimes you have to suck it up, move away from your family and friends, become a nobody, and start pulling in a paycheck. Once you do you can start planning (and saving) for the luxury of living and working in a desirable place.
The takeaway here? Get away from the crowd. In my experience there are at least two good markets for developers, Denver/Boulder CO (Denver being easier than Boulder), and Kansas City MO/KS. I'm not a big fan of Kansas or Missouri (sorry natives, you're all great people), but Colorado is a beautiful place with lots to do outside your cube/apartment. The job markets in both those places are reasonable and you can be relatively well paid even with limited experience. How do they compare with SF/NYC? Not even close, but it's way easier to stand out from the crowd when there is no crowd. Being in the middle of nowhere can sometimes be a benefit.
All that said, good luck.
Good companies don't care if you have a CS degree as long as you can code and think. That said, someone may have embellished the job requirements and if you think you'd be a good fit for a job it may be worth applying anyway.
I'm not sure what the situation is if you have no degree at all, or a degree with no scientific or technical element, but it helps to have evidence of your skills, and whatever your situation it really helps to know people who have a good impression of you and your abilities.
For better jobs boards, look at:
Stack Overflow Careers http://careers.stackoverflow.com/Jobs?searchTerm=&search...
HN Who's Hiring threads. Eg http://news.ycombinator.com/item?id=1659409
Also, check local user groups for whatever languages/technologies you're interested in.
One aspect is the theoretical foundation. You can of course get this by just reading yourself and a transcript doesn't actually prove you know anything but without a CS foundation, the onus is now on you know to prove somehow you're simply a "monkey see, monkey do" cut-and-paste coder.
The other important part is practical. Companies get a lot of CVs. For programming jobs, the most common filter is "has a degree". If you have one, you go in one pile, if you don't, you go in the other (which is often filed in the big circular filing cabinet). What's more, hiring managers may have their hands tied on this one: it could be HR policy or the hiring manager may not even see your CV because HR has already filtered it out (this happens a lot).
After I started working I went back and studied part time to get a degree. I'm glad I did, even if it's major use is to have one less barrier to being hired.
Stackoverflow careers? Seriously? "34 jobs found near boston". How many candidates are looking at these listings? Thousands?
Just imagine a sysadmin turning up with their laptop and demonstrating...
1. Provisioning of servers where they've created the *nix build, deployed a web app, mysql etc
2. They show off their system monitoring capability, take down a few services and then show off their e-mail alerts. Bonus points for twilio integration with SMS :)
3. They then show the backup process they have and how they verify their backups
4. The sysadmin then runs a series of security tests against a server and shows the results
I would hire that guy in an instant
In the case of a sysadmin job, this is how I would do it: start showing some expertise in configuring Linux virtual instances, discuss why and how you manage them, share tips and tricks you learned. That will do you a lot of good on your resume, help you land interviews, and help you convince during those interviews. Especially if you are competing with other college grads with 0 experience, you'll stand out.
Get out and contact the headhunters yourself and work with them and network with all the people you do know and hit them up for positions. They might not have anything at their work but its possible they or one of their colleagues has or knows someone who does have a position open.
Secondly you are taking the BSCS or MS lines in job ads at face value. When they say "Requires a BSCS" what they mean is "Requires a BSCS or experience".
Was this written in the late 90's?
I follow job listing sites almost daily, and I'm just not seeing this. I'm also not seeing it in the volume of headhunters contacting me.
And thirdly, what job listings I do see, they have absurd ideas of what qualifications they require. Yesterday I saw a job listing for perl scripter for system automation tasks requiring a BSCS, MS preferred, and a little while ago I saw a sysadmin job requiring a BSCS.
I'm not in the middle of nowhere, I'm in the Boston/128 area.
So do I have the worst job hunting skills ever or is this guy living in a bubble?