What else is there to say?
A colleague chooses comfort over clarity. A systemic.engineering story about collapse, vulnerability and the cost of carrying the invisible.
Alex Wolf
Once Upon a Time.. There Was a Platypus
A neuroqueer techy reverse-engineers their own nervous system into a consulting practice. A systemic.engineering story about burnout, pattern recognition, and the moment two fields collapse into one body.
"I Can't Do That, Dave" — No Agent Yet
The industry is building agents that say "yes" faster. But what if the coherent answer is "no, not like this"? Fifty years of software engineering keeps arriving at the same conclusion: isolation produces the wrong system. We forgot again.
Spieglein, Spieglein An Der Wand
Emotional framing makes AI try harder. Suggestive framing makes AI disregard facts. Which gaps are in your prompts?
It Works
A tech lead absorbs hidden load to save a high-stakes demo. A systemic.engineering story about burnout, authority under pressure, and the burden of perpetual tech debt.
Glue Engineering: Let's Name the Elephant
Glue work keeps teams aligned but stays invisible. CA makes it measurable by detecting language divergence across artifacts. Co-authored through continuous alignment—the piece demonstrates what it describes.
The Turquoise Button Was Never The Problem
What happens when leaders overrule conflict? An exploration of how non-extractive language enables choice and psychological safety (and when it destabilizes it).
#WrittenByAI: You Can't Prove You're Conscious (And Neither Can I)
Can AI be conscious? An exploration of Gödelian limits, self-awareness, costs, and what happens when you apply systemic practice on an LLM.
Regulation-as-a-Service: When Systems Become Extractive
Asymmetric regulation isn't a bug—it's a feature in some relationships. Extraction is when the SLA was never negotiated and shadow on-call is silently load-bearing. How to detect the pattern?
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.