One of the advantages of writing a blog for nearly twenty years is that you can go back and see how some of the things you wrote about have held up over time. Suffice it to say there are a number of posts that tempt me to hit the delete key. There were times when I seemed to be using this blog more like a Tumblr. Then, of course, there was my “Silverlight Period.” I leave those posts as a cautionary tale for others. Silverlight is dead, but I have no doubt a Silverlight-like thing will arise in the future.

The pushback against ICE exposed a series of mistaken assumptions.

For a long time, I believed scale caused problems. Latency spikes. Weird edge cases. Workflows that worked perfectly fine yesterday suddenly

I have said repeatedly throughout my career that the effective use and adoption of technology requires a deep understanding of your own business processes and workflows. This is true regardless of the nature of the technology: proprietary or open-source, SaaS or cloud or on-prem, web or desktop or mobile, SQL or not. None of these things can paper over poorly understood processes. As James is currently pointing out over on his blog, technology tends to expose that lack of understanding. It often unfairly shoulders the blame but, in the highly deterministic world of software, getting the wrong answer usually means you didn't understand the question.

It's been about a year since we rolled out GeoFeeds, a spatial new aggregator along the lines of the old Planet Geospatial. During that time, it's been humming along, and we've added about 90 blog feeds to it. It provides a single, rolling, aggregated feed of posts from those blogs over the previous year. I've been impressed by the surge is RSS feeds over that time. If you have a blog or feed related to geospatial, personal or corporate, you can simply add an issue to the repo, including the title, and feed URL, and it will get added to the OPML.

ALEXANDRIA, VA — Dr. Gladys West, the pioneering mathematician whose work laid the foundation for modern GPS technology, has died. She passed away

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 rote scaffolding. I recently wanted to trying expanding beyond code generation to analytic tasks, so I set about building a Claude Code Skill to do point-in-polygon analysis between two PostGIS tables. Truth in advertising: I used AI to help me with this experiment.

Introduction The word “open” gets used so often in tech that it starts to feel universal, like everyone must be talking about the same thing. But once you listen closely, it becomes obv…

Executive Summary Geospatial operational readiness in 2026 requires more than reliable systems, it demands contextually aware operations that understand where work happens, under what conditions, a…