Maybe neither of us will ever know when this was written. Live.
Any conversation
ai coding feels like it has reached diminishing returns for me. luna is my default orchestrator, routing work by complexity. in practice, usage lands around 16% luna, 48% sol, 30% astra, and 6% terra. at this point, i care less about each new frontier release. the system already finds a capable model for the job. the frontier is moving beyond my day-to-day work, so i’m happy to settle into predictable models for a while.
code quality is about coupling.
coupling is not a technical property of the code bytes.
code acquires its meaning in contact with the cultural environment, and coupling is about meaning.
two constants with no semantic relationship are nonetheless coupled in pragmatics if they refer to the same domain concept.
if your goal is to minimise the time integral of future work, you must understand your domain: it decides which lines will need changing.
to carve up a codebase is to carve up the world.
A thing I've been doing lately is trying to come to the same conclusions others have without looking their the direct techniques and code. Last night I tried to figure out why people do vector based retrieval for RAG and ended up running these experiments: n0tls.com/…/2026-09-03-i-think-…rag-with-grep.html
I'm still going to do an explore agent.


