This is great advice for all resumes because of the TL;DR problem. Professional resume builders, recruiters, and HR people have all told me the same thing - every single word should be there for a reason. Remember that the person reading your resume is likely reading 10s or 100s of them. If they see a wall of text they will just move on.
You also hit on another point, be specific. For example, I would like to see your shortened version of ArcObjects in a quick points at the top of the resume and then very specific support in following descriptions.
To the OP, so what if you used ArcObjects daily for 3 years, explain exactly what you did with that tech. If you can, use specific numbers (users and dollars tend to jump out).
I used to do that with all my resumes actually. Concise and to the point. Though as I went further along, I started hearing what HR reps looks for and what Recruiters want. They want people to explain more about what they have accomplished. I figured to separate things by knowledge of a certain subject then push it out to what I have built, instead of saying what I built then and what Tech Ive used. Sadly, Im in a bit of a classified environment. So its harder for me to explain my actual work and much easier to explain the tech used.
The first thing you read is that your attributes are "Big Data" "Strong" and "Commenter" why don't you put actionable things? big data is debatably valuable, but the others are just noise
EDIT: Looks like the comment containing salary info was deleted.
* Skill set
* Achievements at last company
* Education
Considering the whole point of this page is to generate leads to request your resume why is it so long? why not keep it vague?
Some of your opening sentences need a lot of work. In fact, just remove words. Keep removing words:
"My experience with ArcObjects is extensive. I have been using ArcObjects for well over 3 years and have been using the framework almost on a daily basis"
= * 3+ years developing on ArcObjects
And this? why?
Python is one of the worlds best interpreted languages. Even though it is more than 20 years old, it is just now coming to the world stage. I use it in most of my crone jobs that need to be completed on a set schedule.
or this
Silverlight and me are like a pea in a pod.
(thats actually quite hilarious - do you mean two peas in a pod?)
Hobbies = irrelevant.