I’m so happy to see @sfgiants.com spring training games.
@james.fee.fm
Geographer who now spends his time on cloud architecture. Engineering Director @Trimble for workflows. Lifelong baseball fan, proud supporter of the San Francisco Giants, and a devoted thalassophile. My Twitter Archive resides at @cageyjames.bsky.social
AI demos are everywhere right now.
Beautiful renderings. Smooth flythroughs. Instant magic.
But magic isn’t a product. Workflow is.
If it can’t survive permitting, budgets, integrations, and reality… it’s just a very good video.
New post:
spatiallyadjusted.com/ai-isnt-the-...
Cloud-native didn’t fail. We just stopped the sentence at “storage” and called it architecture.
Object storage ≠ systems
Containers ≠ workflows
“It scales” ≠ operations
Cloud-native didn’t remove complexity. It just stopped letting us ignore it.
spatiallyadjusted.com/cloud-native...
So no turkey sandwich?
“Self-service GIS” usually means:
You now own all the complexity we didn’t productize.
If users can’t understand what the system is doing without asking a human, it isn’t self-service — it’s unpaid labor.
spatiallyadjusted.com/the-lie-of-s...
“Post-GIS” isn’t about GIS going away. It’s about spatial thinking no longer insisting on being the front door.
Bill Dollins’ post sparked some thoughts I couldn’t shake, so I wrote a response:
spatiallyadjusted.com/post-gis-rev...
We’re not post-GIS. We’re post pretending GIS is the whole story.
This is what people need to understand about the 1%. It’s a different world.
Failure isn’t an edge case. It’s the default condition at scale.
If failure isn’t modeled, named, and exposed, users will invent their own handling.
And that’s where humans sneak back in.
Lessons from Scale #10:
Failure Is a First-Class API
spatiallyadjusted.com/lessons-from...
At scale, observability isn’t an ops concern.
It’s a user feature. The moment someone asks “Did it run?” or “What happened?”, the system has already failed to communicate. Logs don’t build trust. Visible state does.
Observability Is a User Feature
spatiallyadjusted.com/lessons-from...
Every system I’ve worked on had APIs.
None of them actually integrated anything.
- APIs expose verbs.
- Workflows express intent.
At scale, humans become the glue only when systems refuse to remember state.
APIs Don’t Integrate Systems. Workflows Do.
spatiallyadjusted.com/lessons-from...
Revolution starts when grandma’s sit on corners in Phoenix with signs that say deport Steven Miller now. You can’t fight a grandma.
Sometimes it just works out.
Wordle 1,683 3/6
⬛⬛⬛⬛⬛
🟨⬛⬛⬛⬛
🟩🟩🟩🟩🟩
Most spatial systems don’t fail loudly.
They fail politely — and a human fixes it before anyone notices.
That’s not automation.
That’s a Wizard-of-Oz system.
Humans are not a scalable integration pattern: spatiallyadjusted.com/humans-are-n...
Standards don’t usually fail because they’re wrong. They fail because we stop being honest about what they’re doing for us.
Schemas harden. Extensions multiply. Humans quietly become the glue.
spatiallyadjusted.com/lessons-from...
COG + STAC isn’t a stack, it’s a contract. A contract about access patterns, about metadata. About admitting humans can’t be the glue at scale. Cloud-native didn’t win because it was elegant. It won because it was honest.
🔗 spatiallyadjusted.com/cog-stac-isn...
Scale doesn’t break systems, it reveals the one you actually built.
At small scale, humans are the glue.
At large scale, assumptions become outages.
If your system only works because someone “knows how it works”…. that’s not design. That’s babysitting.
spatiallyadjusted.com/lessons-from...
I’ve spent most of my career watching GIS get blamed for problems it didn’t create. The map wasn’t wrong.
The organization just didn’t want to look at what it was showing.
spatiallyadjusted.com/gis-doesnt-c...
Orchestration works great as “plumbing” until users care about outcomes. Then it quietly becomes part of your product, whether you planned for that or not.
spatiallyadjusted.com/lessons-from...
“The GIS is wrong” usually means “we never agreed on what right looks like.”
A few thoughts on why most GIS problems aren’t actually GIS problems: spatiallyadjusted.com/most-gis-pro...
Post #2 digs into a long-held myth: that interoperability is mostly a file format problem.
Spoiler: formats matter, but workflows matter a lot more.
spatiallyadjusted.com/lessons-from...
#GIS #Geospatial #SpatialWorkflows
I’ve started a new series on Spatially Adjusted called “Lessons from Scale.”
It’s about what actually breaks (or changes) when spatial tech moves from small, local use to enterprise scale — across GIS, CAD, BIM, workflows, and people.
Post #1: spatiallyadjusted.com/trimble-spat...
Post #2 digs into a long-held myth: that interoperability is mostly a file format problem.
Spoiler: formats matter, but workflows matter a lot more.
www.spatiallyadjusted.com/lessons-from...
#GIS #Geospatial #SpatialWorkflows
Well, when I was younger, I was a huge rams fan. They moved to St. Louis and now I could care less about them.
Boy, these two look like a lot of fun!