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
Putting a slide deck together (outside of work), despite agreeing with Tufte on this matter. I’ll also create a handout that tells the story better than the slides and deliver that, too, but was asked to produce a slide deck, and I think that’s part of the “effort theater.”
Using Beamer for the slides, but not a theme that looks like Beamer because humans have eyes.
Avui tenia una reunió llarga de moltes hores, d'aquelles en les que una escolta passiva és suficient durant la major part del temps. He aprofitat el temps per implementar una sincronització en dues direccions entre el meu calendari i el meu sistema de notes en markdown (Emacs Howm). He fet el pla amb Argon (tinc pocs tokens al dia amb la subscripció que tinc), amb feedback meu, i després Gemini Flash l'ha implementat quasi a la primera.
Today I had a long meeting of many hours, one of those where passive listening is enough for most of the time. I took advantage of the time to implement a two-way synchronization between my calendar and my markdown note system (Emacs Howm). I made the plan with Argon (I have few tokens per day with the subscription I have), with my feedback, and then Gemini Flash implemented it almost on the first try.


