I didn’t get into programming through computer science.

I got into it through HyperCard.
Stacks. Cards. Scripts. Buttons.
You could actually see how software worked, which apparently we decided was too simple and replaced with 47 layers of frameworks and build systems.

My first app?

A fly-fishing tackle box database for my dad, uploaded to GEnie.

New post:
https://spatiallyadjusted.com/hypercard-taught-me-software-isnt-magic

If you’ve never seen HyperCard, this video is worth your time:
https://www.youtube.com/watch?v=hxHkNToXga8

AI is incredible at generating output.
What it’s not great at (yet) is generating outcomes.

In spatial systems, the hard part isn’t the rendering. It’s the workflow — the metadata, the contracts, the integrations, the discipline that makes something buildable.

AI isn’t the product. Workflow is.

https://spatiallyadjusted.com/ai-isnt-the-product-the-workflow-is

#AI #GIS #SpatialComputing #ProductStrategy

Cloud-native didn’t fail. We finished:

• storage
• compute
• deployment

We skipped:
• workflows
• failure modes
• observability
• accountability

Then we blamed “complexity.” Cloud-native didn’t create it. It just made it visible.

https://spatiallyadjusted.com/cloud-native-didnt-fail

#CloudNative #GIS #Architecture #Scale #Systems

Every modern GIS platform claims to be “self-service.” What they really did was move complexity out of sight and onto users.

Invisible workflows, optional metadata, silent failure — and one poor human who “just knows how it works.”

https://spatiallyadjusted.com/the-lie-of-self-service-gis

I really enjoyed Bill Dollins’ recent Post-GIS Revisited post — not because it settles the question, but because it refuses to.

It got me thinking (again) about how GIS didn’t disappear so much as dissolve into workflows, metadata, and systems that don’t need heroics anymore.

I wrote up a few thoughts as a continuation of the conversation:
https://spatiallyadjusted.com/post-gis-revisited-again

Curious how others are experiencing this shift in practice.