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.
Any conversation
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.
a szerveren lรฉvล cookie adatokat รฉs egyรฉb nyomkรถvetล sz@rokat is a Google kezeli, รฉn nem igazรกn szoktam ezekbลl lรกtni semmit, se ip-t, se semmit, a Google inkรกbb keresลmotor, mint mestersรฉges intelligencia alkalmazรกs, de ma mรกr hibrid technolรณgiรกval dolgozik minden MI รฉs keresล
Google also manages the cookie data and other tracking s@rs on the server, I don't really see anything from these, no IP, nothing, Google is more of a search engine than an artificial intelligence application, but today all AI and search engines work with hybrid technology
a constant, existential pull
so old I couldn't tell you the end
or draw its shape
between kind acceptance
and striving, struggling, writhing, climbing
learning, growing, discontent
"do you feel this way, too, at endless war with longing itself?"
but the birds and trees and ants and wind
in their own marvelous design
don't reply

