I agree w/ everyone else that code on the resume itself is a bad idea. Your resume is where you sell yourself - code is not going to convince that manager that you are the best candidate for the job. Your skills, accomplishments, awards, education, and experience (not necessarily in that order) are what gets you the job. Put your code samples on your homepage - you'll most likely need them at some point.

A resume is the time to boast (a little) about how great you are. As noted here and on that other site, real world experience counts for a lot. Even if it was not paid, ie. open source projects. Can you work w/ a team? Can you manage deadlines? Can you juggle multiple tasks? Can you handle intense pressure? Are you a self starter? These are the types of questions that seem to be coming up in my interviews. The better you can show the answer to these questions is "YES!", the easier it will be to find a job.

Don't be afraid to trumpet your abilities. The trick is finding the line between a good sell and being an arrogant jerk. If you think you did something cool or unusual, say so. In interviews, I always seem to get asked "What was your favorite/most interesting project?". Have a good answer ready. It shows if you make it up on the spot, although improvisation is essential to tailor it to the wants of your interviewer.

And NEVER turn down a chance for an interview, even if you don't think you'll get the job. You need the experience of interviewing. Each one can be a learning experience if you let it. You have an advantage over the guys who haven't had to interview in 10 years because they are so rusty. :-)

Best of luck in finding a job. Things seem to be picking up somewhat here in Boston. I hope it's true for the rest of the country as well.