This is the best post I have seen so far on this topic.
Before I had ten years as a certified MCP PC tech, and Mac tech, I was an HR person with a BA in the field of HR/management/labor and employment law.
Before I knew much about computers other than being a proficient user, the only hint that I knew that somebody knew anything about computers were people who were either certified through Microsoft, CompTIA (A+ particularly), and Cisco. The other good thing on a resume as far as degrees were a computer science, computer engineering, software engineering, management information systems, or IT degree.
Back then, like most purely HR people are now, I didn't know about certain more specialized jargon like Perl, wide area networks vs. local area networks, DBAs, SDK, or some of the more obscure titles such as a Certified HP printer technician, Certified Novell Associate, or CISSP. While good to have, these things can go over many an HR person's head, especially if you have to look at hundreds of resumes.
But most HR people should know the common industry standards like C++, A+, Network+, MCP, MCSE, Oracle, and Cisco. But when you get proficiency, certifications, or degrees, don't just use acronyms other than BA/BS, AA/AS, MA/MS, or PhD.
Do not automatically assume the HR person will think A+ is a hardware certification and not a computer language like C++. Also don't use the term MCP or MCSE but spell out what they are, Microsoft Certified Professional and Microsoft Certified Systems Engineer on a resume. It's those tiny pesky details on a resume like "Microsoft" which jump out and grab the attention of an HR person. The HR person will not be concerned about whether the particular Microsoft certifications test(s) were hard or not. They won't care if you went to a technician's trade school for the certification, university, or self-studied and then passed the test(s). The HR person will equate the word Microsoft with high tech and Bill Gates. Period.