Technologies: Python, Ruby, C, C++, C#, JavaScript, TypeScript, PowerShell, Flask, SQL, PostGIS, Shapely, Unity, Unreal Engine, multiple assembly/machine languages, Windows user code and kernel drivers, Google Maps and other map APIs, geographic and airspace data
Hi, I'm Michael Geary. I've programmed in many languages and environments over the years. Some of my current interests are:
• Developer experience. I love helping my fellow developers solve problems, and building tools to make their jobs easier and more enjoyable.
• Aviation and geographic data. For example, airspace and obstacle data importers for Wing; election results and voter information maps for Google; many interactive maps for other companies.
• Hardware interfacing. In a way, I am a "full stack" developer, but my stack may involve a front end to a piece of hardware rather than the cloud. I first got into programming via ham radio, so RF hardware remains an interest.
• Designing and building APIs. Too often an API is designed by exposing the internals of whatever system provides the API. My philosophy is the opposite: start with the apps. I like to build a series of sample apps before starting on the API. This way I can imagine what API will make those apps and others like them easy to build.
• Talk with users! I don't like to sit in a back room cranking out code. I want to make sure it's the right code for what my users need, and that it's easy to maintain and improve as we learn more about what they want.
Technologies: Python, Ruby, C, C++, C#, JavaScript, TypeScript, PowerShell, Flask, SQL, PostGIS, Shapely, Unity, Unreal Engine, multiple assembly/machine languages, Windows user code and kernel drivers, Google Maps and other map APIs, geographic and airspace data
Hi, I'm Michael Geary. I've programmed in many languages and environments over the years. Some of my current interests are:
• Developer experience. I love helping my fellow developers solve problems, and building tools to make their jobs easier and more enjoyable.
• Aviation and geographic data. For example, airspace and obstacle data importers for Wing; election results and voter information maps for Google; many interactive maps for other companies.
• Hardware interfacing. In a way, I am a "full stack" developer, but my stack may involve a front end to a piece of hardware rather than the cloud. I first got into programming via ham radio, so RF hardware remains an interest.
• Designing and building APIs. Too often an API is designed by exposing the internals of whatever system provides the API. My philosophy is the opposite: start with the apps. I like to build a series of sample apps before starting on the API. This way I can imagine what API will make those apps and others like them easy to build.
• Talk with users! I don't like to sit in a back room cranking out code. I want to make sure it's the right code for what my users need, and that it's easy to maintain and improve as we learn more about what they want.
I have a couple of tricks that get people to talk to me.
Well, they're not really tricks, just things I do anyway.
One is that I wear an aloha shirt every day, and I shop at Trader Joe's.
Quite often someone thinks I work there and asks me where to find something. I usually know where things are, and if I don't, I find them someone who actually does work there.
One time the guy restocking the freezer said, "Nice aloha shirt! I bet people sometimes ask you where to find things."
30 seconds later, a lady walked up to me and asked if we carry organic bread. So I walked her over to the bread section and pointed out some organic options. Then back to the freezer section: "You were right!"
Another trick is to take my cat Oakey for a walk in his cat stroller. People see the stroller and expect to see a baby in it, and are surprised to see a cat! Children walking with their parents especially love to see Oakey, and he enjoys the attention.
Sometimes you just have to seize the moment. Last year I was at a friend's company summer picnic. One of her colleagues brought her ten year old son. He was wearing an astronomy T-shirt. They were sitting at another table, and as they got up I asked him, "Are you into astronomy?"
"Yes."
"I have a very important question for you. Pluto is still a planet, right?"
"Yes it is!"
We high-fived and I said, "Welcome to Team Pluto!"
We've seen each other at subsequent company events. It is always fun to hang out with a fellow astronomy enthusiast of any age.
I think an important parts of this is that "talking to someone" doesn't have to mean a long drawn-out conversation. Even just a few words back and forth is meaningful.
Some of our SF Peninsula bank branches now have two tiers of ATMs:
• The traditional through-the-wall machines that you can access from outside.
• Inside the branch, heavy duty standalone machines that dispense much more cash and more of a variety of bills. These are only accessible when the branch is open, unless you break glass.
Remote: Yes, or hybrid if nearby
Willing to relocate: Possibly
Technologies: Python, Ruby, C, C++, C#, JavaScript, TypeScript, PowerShell, Flask, SQL, PostGIS, Shapely, Unity, Unreal Engine, multiple assembly/machine languages, Windows user code and kernel drivers, Google Maps and other map APIs, geographic and airspace data
Résumé/CV: https://www.geary.com/resume.html or https://www.geary.com/resume.pdf and https://www.linkedin.com/in/michaelgeary/
Email: mike@geary.com
Hi, I'm Michael Geary. I've programmed in many languages and environments over the years. Some of my current interests are:
• Developer experience. I love helping my fellow developers solve problems, and building tools to make their jobs easier and more enjoyable.
• Aviation and geographic data. For example, airspace and obstacle data importers for Wing; election results and voter information maps for Google; many interactive maps for other companies.
• Hardware interfacing. In a way, I am a "full stack" developer, but my stack may involve a front end to a piece of hardware rather than the cloud. I first got into programming via ham radio, so RF hardware remains an interest.
• Designing and building APIs. Too often an API is designed by exposing the internals of whatever system provides the API. My philosophy is the opposite: start with the apps. I like to build a series of sample apps before starting on the API. This way I can imagine what API will make those apps and others like them easy to build.
• Talk with users! I don't like to sit in a back room cranking out code. I want to make sure it's the right code for what my users need, and that it's easy to maintain and improve as we learn more about what they want.
Open to full time or contract.
I look forward to talking with you!
reply