Ai

Every codebase has two states: the code, and the lie we tell about the code. Most documentation systems make the lie comfortable. One I came across recently doesn’t. Documentation has always been the thing engineering teams promise to do and quietly skip. Sprint deadlines win, the wiki rots, the README becomes archaeology. We all know the cycle. Recently I came across a project (by Franco Dominguez Noriega) that does it differently — and the difference is not just “we tried harder this time.” It’s a structural change that only makes sense in a world where AI agents are part of the development loop. After spending some time with it, I’m convinced the pattern is worth sharing, because it solves the documentation-decay problem in a way I haven’t seen before. ...

An engineer’s conjecture on distributed biological intelligence, dreams, and the uncomfortable trajectory of AI In computing, thick clients carry their own processing power, storage, and local decision-making — but they become dramatically more capable when networked. A thought lodged in my head recently and wouldn’t leave: A human brain looks remarkably like a thick client. Andy Clark and David Chalmers argued in their “Extended Mind” thesis (1998) that cognition doesn’t stop at the skull — it extends into notebooks, tools, and cultural artifacts. They didn’t use the client-server vocabulary, but the implication is the same: the brain is a node in a larger system. ...