Yes, You Need to Code

Over the past year, I’ve been involved in searching for GIS analysts a number of times. As a result, I’ve noticed a few patterns:

  1. There are a lot of analysts out there looking for jobs. Every time I run an ad, I get at least 100 resumes from people of various levels of experience and education.
  2. The vast majority of those that I call to pre-screen have not done any meaningful coding of any kind. This includes Python, which has been shipping with ArcGIS for several versions now.
  3. Of those that do have some coding experience, many do not show it on their resumes. I find this particularly interesting as I can’t imagine why a person would choose not to list all relevant skills or experience.

I am very publicly on the record that I think some form of coding skill is essential for any GIS analyst entering the workforce today. My reasoning here is fairly straightforward.

Continue reading “Yes, You Need to Code”

GeoIQ & Esri

Okay, everybody calm the hell down. Anyone who thinks that the Esri acquisition of GeoIQ is strange hasn’t been paying attention to two things: 1) the direction that Esri says they want to go and 2) what the GeoIQ platform really is. I would be very surprised if GeoIQ becomes the 2012 version of Atlas GIS. This acquisition/merger makes more sense than may be initially apparent.

It’s no secret that I’ve worked with Esri tools for a long time and my recent work with the GeoIQ platform has been well-documented on this blog, including work integrating the two platforms at the API level. Based on what I’ve seen from both companies, here are thoughts on why I think this move makes a lot of sense: Continue reading “GeoIQ & Esri”