Developer tooling
The umbrella concept of this spoke: the systems-level tools and libraries a programmer’s work flows through that aren’t the application code itself — the infrastructure that builds, versions, and moves software. It is broad by construction (see synthesis); the founding sources stake out three of its layers, and others are open.
The layers
- Language toolchains & compilers — turning source into something runnable: compilers, transpilers, typecheckers, linkers. Founding example: typescript-7-go-compiler (the TS compiler rewritten in Go).
- Version control — storing and sharing source and its history. Founding example: lore (Epic’s Rust VCS for code + large binary assets).
- Serialization & data-interchange formats — laying structured data out to move between processes and machines. Founding example: yaff (Yandex’s C++ zero-copy Protobuf-ecosystem format).
- Open corners (no source yet): build systems, package managers, IDE/LSP tooling, dependency managers.
The thread tying them together (so far)
Across the founding three the recurring move is performance won by removing a layer of overhead, via a systems language — Go for the TS compiler, Rust for lore, C++ for yaff — and all three are big-tech open-source (Microsoft, Epic, Yandex). See synthesis for whether that holds up as the real theme or is an artifact of three speed-led launches.
Boundary
A coding agent or harness routes to agentic-tooling-wiki; the compiler / VCS / format / build tool it operates on routes here. Instruction-level bitwise tricks are bit-manipulation-wiki; front-end delivery budgets are webperf-wiki; operating production systems is platform-ops-wiki.