Geospatial technology, markets, and practice
I've been doing more (a lot more) with Claude Code lately. With its subagents and skills features, it's become more customizable and powerful. I can really dial it into doing things the way I want them done, which accelerates my development and quickly gets me to where I am focused on important behaviors, rather than … Continue reading Spatial Analysis with Claude Code
Earlier in my career, I was working on an infrastructure protection task and we were reconciling data from several sources that addressed the same road network. The data from the locality was authoritative, but it lacked some information we needed so we were conflating other data to the linework. I commented on the general lack … Continue reading Metadata Rising
I have no problem with vibe coding. Yes, you can make bad code with it, and quite easily. The worst way to vibe code is to issue a monolithic prompt like "Build a word processor with the features of Microsoft Word." But using techniques like chain-of-thought or plan-and-solve prompting in an iterative manner can yield … Continue reading Vibing Adjacencies
The time since I've last posted has been quite busy. I've completely recovered from my previous eye issues and have been able to start traveling again. In fact, I'm writing this post from a hotel room. In addition to my consulting work at Cercana, I took on a role as the CTO of Photometrics AI, … Continue reading Geospatial, AI/ML, and Infrastructure
Depending on your point of view, "vibe coding" - using generative AI to iteratively develop code by using natural language to describe desired functionality - is either revolutionary or the slippery slope to deploying poor, irresponsible software. While both viewpoints have merit, I fall somewhere in the middle. As a programmer who is approaching 50 … Continue reading “Vibe Coding” a Mock API