Sign in Subscribe

Topic

Tech & Product

A collection of 10 issues

Regulation-as-a-Service: When Systems Become Extractive

Asymmetric regulation isn't a bug—it's a feature in Parent-child, Therapist-client, Teacher-student relationships. Extraction is when the SLA was never negotiated and shadow on-call is silently load-bearing.

#WrittenWithoutAI: When Meaning-Making Becomes Embodied Labor

"Hi, I'm your friend," says the LLM. But who pays the embodied cost of AI-driven sense-making? A systemic engineer writes without AI. Then asks one to respond.

Tech Debt Isn't Bad Code—It's Encoded Legacy Patterns

Tech debt is legacy patterns reproducing. In your code. Your process. Your team. Why code reviews keep finding the same problems—and better questions to ask.

Who invited the agent? Oh God.. (Smith will suffice.]

Agentic AI collapses ambiguity without a body. This essay cuts through AI agent hype to ask the ethical question no system scaling agents wants to answer.

Unmanaged Ambiguity Kills Your Product (And Teams)

Why "clear" tickets still fail. Learn how constraint-based development (OBC) sharpens requirements, aligns teams, and leads to quieter delivery.

Becoming an Observer in Human Systems

Why effective post-mortems and incident management fail under pressure—and how regulation, not authority or process, restores coherence under load by slowing time, holding silence, and making language a deliberate intervention.

AI Did Not Take Your Agency. You Handed It Over]

An essay on generative AI and LLMs that reframes language as action—exploring agency, precision, and jurisdiction in socio-technical systems under load.

Your Team Is a Distributed System

Model your team as a distributed system. Learn why culture is structure—not vibes—through message passing, locality, loss, asynchrony, and non-linearity under load.

SRE for Human Systems Under Load

systemic.engineering: an embodied site reliability engineering discipline for human systems, focused on coherence under load, regulation, and language as infrastructure.

On Fragmentation: Tech Debt Is a Coherence Problem

Tech debt isn’t bad code — it’s fragmented reality encoded into software. Learn why coherence, not cleanliness, determines system stability under load.