Research

Every page on this shelf is an instance of one relation: 2 ↔ 3 — two different things in bidirectional tension, neither reducible to the other. Engineers and designers. Humans and LLMs. Reverence and proof. The failure mode is always the blanket war, where warming one side freezes the other; the fix is always architecting the relation.

House covenant: every claim here is checkable — quotes carry sources, numbers carry measurements, myths get caveats. If you catch a verse that doesn't hold, tell me — that's the whole point.

Why game engines throttle their strongest users — written by someone who paid the tax in friendships, mental health, and midnight commits.

• Heresy I: Why I left Unity

  Game engines optimize for the people who can't code — at the expense of their strongest users. A personal archaeology, with commit hashes.

  2026-07-15 game-enginesunityarchitecture

• Heresy II: The Blanket Problem

  Engines treat programmer-experience and designer-experience as a zero-sum tug of war. Web development signed a peace treaty twenty years ago. Game engines never did.

  2026-07-15 game-enginestoolinggit

• A Monorepo of Micro-Libraries

  A CMake workspace that behaves like a .sln: drop a lib_ folder in and everything wires up — engine-agnostic C++ cores with thin C shims, and every claim on this page compiles.

  2026-07-21 cppcmakearchitecture

• One Library, Every Engine

  Opaque handle, structured result, out-params, and a hard rule: exceptions never cross the ABI. Plus the six defects — three of them latent ABI bugs — that a '30-minute fix' turned out to be hiding.

  2026-07-21 cppc-apiabi

Rules belong in compilers, dignity belongs to people — team tooling, human/LLM symbiosis, and engineering around a fragile brain.

first texts under consecration △○▽

New research lands in the RSS feed — the old-web way, no algorithm between us.