Mano Marks is a Staff Developer Advocate on the Google Developer Platform team. He works to help developers implement Google’s APIs in their applications. He has a Masters in History, and another in Information Management and Systems. His career has taken him from database management at non-profits, to keynote addresses at Google Developer Days around the world. Mano has been with Google for 8.5 years, and was the founding member of the Maps Developer Relations team, working back then with KML and then the Maps API. Now he works across the Google Developer Platform. You can find him on Google+, Twitter, and Github.
Interviewer’s note: In 2013 CalGIS had the privilege of getting Mano Marks (@ManoMarks) to speak at our conference. Since then, I’ve found out how much more of a geohipster he was than I realized at the time. Thanks, Mano, for spending some time answering questions for the GeoHipster readers!
Mano was interviewed for GeoHipster by Christina Boggs.
Q: You have degrees in history as well as in information management and systems. How did you get into the geospatial universe?
A: Of course I’ve always loved maps. Who doesn’t? When I was a kid, I had a subscription to National Geographic, and I pored over the maps trying to understand them. I was really into games, role playing games and board war games, which were really map-related. Match that with my Masters in History, where I focused on Eastern Europe, where the map was constantly changing, and I was set up to try to crave knowledge of the world from a spatial point of view. I just never considered it from a career point of view.
I got my Masters from the School of Information at UC Berkeley in 2006. At the time, XML was the major data interchange format and I spent a lot of time understanding the XML universe and document construction. So when I started at Google on what became the Developer Relations Team, they had me work on KML. So I backed into it, but as soon I was there, I started learning everything I could.
Q: One of the neat things about the geohipster community is how diverse we are. You’ve been with Google for more than eight years now, what do you do with them?
A: I work on the developer relations team, helping developers learn how to use Google’s developer platform in their applications. This resulted in spending a lot of time on the road for a few years, talking to tens of thousands of developers around the world. One trip in 2011, I literally flew around the world over the course of a month, from San Francisco to China to Australia, Tel Aviv, several stops in Europe, and then home to San Francisco.
Recently, I’ve worked more internally, helping out other members of the team and working on code samples. I helped out on this project, which shows developers how to create sites using JSON-LD, Web Components, and Schema.org markup. Of course there’s a strong mapping component to it.
Q: In times past you have functioned as a liaison between developers and geofolk. If you could give advice on how these two groups could better interact together, what would you say?
A: Honestly, I’d say to geofolk it’s time to learn how to code. There will always be a place for people who are GIS specialists. And, more and more GIS-only folks are getting left behind by focusing on just using complex applications to create a map that is divorced from everything around it. The map is important — it’s a star in whatever platform you’re using. But it’s just a piece of what’s going on. Location, identity, interaction, and more are where people are spending their time. The vast majority of developers using maps don’t want to know how the maps technology works, they want to know that it’ll be stable, and provide their users with what they need.
Q: Google Maps just turned 10! I was just reading an article from Directions Magazine where Diana S. Sinton said:
“Over the last decade, what Google has done to build up the public understanding and awareness of maps and mapping, particularly through the web, has been priceless for GIS. They made the inaccessible accessible, and produced a common point of reference to be able to communicate about GIS. “It’s a little like Google Earth” may be one of the most effective GIS conversation starters ever. Whatever may happen to that technology in the future, it will have left an indelible cultural impact.”
She’s right, it was a change in our culture. What do you think is going to be the next thing imprinted on our culture? Any upcoming developments that you’d like to leak on GeoHipster first?
A: Ha ha, yeah…unfortunately I can’t leak anything. And I can say that the core technologies that our platforms are built on are evolving at a rapid pace. We carry around these super computers in our pockets. I’m using a Nexus 6 right now, which is akin to having a small laptop in your pocket, both in power and size. People have talked for years about “location-based apps” but that time has come.
And what’s amazing to me is how much people just expect it. It’s a little like the early days of Google Earth, when people would say to me “My Google Earth is broken. I left my car in the driveway but it doesn’t show up when I zoom in on my house.” People now get confused when there’s a new business that hasn’t shown up yet in their app. I think we’re going to see a lot more of, well, I wouldn’t say “real-time” data in maps, but more up-to-date data.
Q: You put Mountain View on the GeoHipster map. I think of Mountain View for Shoreline Amphitheatre but I drive by Google every time I’m going into the parking lot there. Silicon Valley has been the driver for tech and geo trends and now I might even extend the sphere to the entire Bay Area (San Francisco Bay Area). Do you think your region is going to continue to drive tech and geo trends into the future?
A: I absolutely think that it’ll be a big driver of world tech. Fortunately for Google there are smart people who like to work everywhere. I just spent a year in the Zurich office and loved it. I think you’ll increasingly see developers in countries like Mexico, Brazil, Kenya, and other countries contributing to driving tech.
A: Hmmm…I definitely think that there is a coolness/hipness factor to many new technologies. I don’t think that means they are not important or really good at what they do, but remember when XML was the big thing? Sure, it’s still used a lot, but it’s not growing dramatically. Or PHP? There’s a language whose time in the sun is gone. What I wonder about instead is what is the next HTML? That was the most important game changer, it made creating a presentation easy, super easy. KML did that for geospatial data, to an extent. I’ve seen a lot of people who were not developers create KML files and really get into it. But what’s the next thing that someone who doesn’t really understand programming can get into? What can they use to create something that communicates with millions? That’s the real game changer.
Q: I’ve seen you post cool pictures and photo spheres from your travels. Many of the most hip of the geohipsters have passion projects that they’re able to either incorporate into their work or they work on outside of work. What are you working on right now?
A: You know, the last thing I worked on was the semantic markup plus web components project. I wrote a small reference Node.js app to take arbitrary data from a MySQL database and return it as a JSON-LD feed in Schema.org markup. Yes, Node.js is very hipsterish right now :-). I think the question of transforming data to semantic markup in non-XML format is not well settled. There aren’t great libraries for it — in part because JS developers have so many frameworks already, I think they’re afraid of something complex and potentially slow. Especially if it smacks of XML.
That question interests me, but that specific project is wrapping up, at least on my end. So I’m not sure. I am really interested in photography, games, and old maps. One thing I wish someone would do is develop a really good way to OCR old maps to capture location data that we don’t have any more. I’m not sure that’s me, but if anyone has any ideas that would be great.
Q: Last question, while you’ve got the ear of the geohipster community — do you have anything you’d like to share?
A: Pity the poor developer. Remember that creating a new data format doesn’t solve all your problems. Chances are it just creates more.
Most geohipster types I know code, but if you don’t code, start. And spread the word.