OMG, it's the acronyms!

Sometimes rappers use spelling to showcase their skills: criminal record (P.I.M.P), bad spelling (D.o.double-gee) or, for lack of imagination, their name (M.e.t.h.o.d.). Sometimes it's funny and sounds cool, but sometimes it's just retarded (yeah, pimp, I mean you).

Sometimes IT people use spelling to showcase their skills as well. It's not as stupid (yeah, pimp, you again) or as funny as in rap music, but sometimes it can help you stand out. Of course, a geek uses only the acronyms, without the embellishing epithets; he's not a ho-pimping-CCNP or an RHCE that's done time, yo. This additional info would make resumes stand out, but probably not in the desired direction. HR is not MTV. Alth... no, nevermind.

The problem is that, just like in rap music, acronyms do not quite reflect reality all the time; they may be the only interesting bullets in your resume and land you on the job. Or you may not have them on the resume, although you have the skills, and don't get the job. In the latter case it only affects you, in the former it can affect others.
A guy I used to work with once interviewed for a DBA position. For the "technical evaluation" this lady pulled a book and started asking him SQL questions. She asked, he answered, she checked his answers in the book and then asked again. Things were going great, until one answer was not like in the book, and things didn't go so great after that. His answer was correct but it wasn't "like it says here". A classic wtf moment. Any attempts to explain were in vain, so he tried to get the best of this, as him getting the job was already out of the question at this moment. He took the book from the table, and said "OK, I will ask you some questions now, just to see how well you actually know SQL". A few embarrassing moments later, the interview was over.
Most likely the job went to the first candidate that had read the book (or to the CEO's nephew).

Reading books pays off, after all.