The ur-post
Explore the concept of the ur-post and its role in microblogging, sources, and references in the digital content landscape.
One thing I’ve been wondering about (in all my musings on #microblogging) is the relationships among sources and references. Earlier, I speculated that all blogging is only reference, because an #rss feed is just a sign to a #blog post.
Interestingly, it’s a robust sign. Some feeds are so robust that they are copies of their source. There is no need to “click through” to the source, because the same information is in the feed.
Even if feeds are referrers, to what do they refer? The refer to sources.
Some sources are copies of other sources. Once a source item is copied, there’s no need to trace the feed back. A copy is just as good.
But what if there are no copies? And what if the feeds are not copies, either? Then the feeds just point back. They point back, even through many feeds, to the source. If content is not replicated, then there is always one source.
I call this the ur-post.
Why customer tools are organized wrong
This article reveals a fundamental flaw in how customer support tools are designed—organizing by interaction type instead of by customer—and explains why this fragmentation wastes time and obscures the full picture you need to help users effectively.
Infrastructure shapes thought
The tools you build determine what kinds of thinking become possible. On infrastructure, friction, and building deliberately for thought rather than just throughput.
Server-side dashboard architecture: Why moving data fetching off the browser changes everything
How choosing server-side rendering solved security, CORS, and credential management problems I didn't know I had.
The work of being available now
A book on AI, judgment, and staying human at work.
The practice of work in progress
Practical essays on how work actually gets done.
The day the fleet shipped everything
One session. Three products. Seventy-plus features. What happens when you stop planning and start dispatching.
Knowledge work was never work
Knowledge work was always coordination between humans who couldn't share state directly. The artifacts were never the work. They were the overhead — and AI just made the overhead optional.
Context as facticity: stigmergic and ontological perspectives on AI agent coordination
The AI multi-agent coordination literature is doing analytic philosophy without knowing it. Continental philosophy — Heidegger's facticity, Gadamer's fusion of horizons — explains why a chat channel works better than a constitutional framework. The answer involves digital pheromones and the fact that AI agents have facticity too.
ActivityPub spec
Explore the ActivityPub specification to understand how to write effective specs and enhance your web development skills.
The semiotics of networked content
Explore how networked content transcends platforms, focusing on the significance of signs over replication in the evolving digital landscape.
Embracing the AI workforce
Discover how AI enhances the workplace by fostering collaboration and spontaneity, offering a fresh alternative to traditional office dynamics.