A Team of One, Running Two Teams
The initial implementation of Omnist, a tested, open-source Python library, came together from a 16-year-old PhD paper in two weeks — one person, part-time. That fact tends to get read as “AI writes code fast.” It doesn’t quite explain it. What actually happened is that I ran two teams during those two weeks, not one — and I was the only human on either of them. Two layers, two teams Split any R&D project into two layers. Conceptualization: interpreting the idea, deciding what’s true, choosing what to build, naming things so they make sense. Materialization: turning a decision into working code, a test that proves it, a release someone can actually install. ...