I hate crawlers that donโt advertise theyโre crawlers. โn badly written. They donโt respect the canonical URLs so they keep getting themselves into a loop instead of actually crawling the site properly. They make the logs really hard to read. Canโt block them theyโre distributed.
Any conversation
I notice that language models are much better at programming than at writing. This is largely because, in programming, they have a closed feedback loop that allows them to find errors. Writing is much more complicated because the feedback is much more diffuse and delayed over time. In fact, it is often not well-defined.
When I read about in reputable , I relate to almost everything that is described (keeping in mind that no two autistic people are alike). However, I always read the sections on with bewilderment. I don't identify either with the obsessive need to make eye contact, which UK and US books often mention as behavior, or with the difficulties in making it.
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.
Yesterday I with help from the clanker, as an experiment, ported a web app from go+postgres+svelte to ari+duckdb+htmx served locally by busybox httpd. Itโs an analytics โdashboardโ so the stack makes sense. So far looks good. Now I work on the code in vim to make it mine. I want fewer layers of abstraction and less complexity, and this is a learning experience to that end.


