The semiotics of networked content
Explore how networked content transcends platforms, focusing on the significance of signs over replication in the evolving digital landscape.
Working on content interop super-ontology in the #mastodon, #micro.blog, #twitter, #feedland, and #wordpress multiverse.
Posts are actual pieces of content. They are mostly made on the platform where you find them.
Timelines are views into (yours and others’) posts. These views are made possible by transmitting information about the post via #RSS (or something else) and aggregating into a timeline. Timelines can include feeds from yours or others’ sources.
What’s interesting is that timelines can also be published and consumed, also via #rss.
This means that, if you consume a feed, you don’t know if the source-content in the feed originates with that feed. Feed elements could “pass through” as signs to their sources. In fact, it doesn’t even matter.
In this sense, we don’t want to replicate content around the networks, we want to replicate signs.
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 smartest code you'll ever delete
The most dangerous kind of waste isn't the thing that doesn't work. It's the thing that works beautifully and shouldn't exist.
The first real user breaks everything
Your product works until someone actually uses it. The gap between 'works in dev' and 'works for a person' is where most systems fail — and most organizations avoid looking.
The loop nobody bothers to close
Most systems observe. Almost none learn. The difference is a feedback loop — and the boring cleanup work that makes it possible.
ActivityPub spec
Explore the ActivityPub specification to understand how to write effective specs and enhance your web development skills.
The ur-post
Explore the concept of the ur-post and its role in microblogging, sources, and references in the digital content landscape.
Embracing the AI workforce
Discover how AI enhances the workplace by fostering collaboration and spontaneity, offering a fresh alternative to traditional office dynamics.