Intro: Wisen to create a recursive learning loop for my coding harness. Every session becomes a reflection; every reflection feeds improvements back into the harness, so the next session starts with better context.
Any conversation
An interesting thought: historically, a major consideration for companies choosing what to use is how many engineers use it (because that will make hiring much easier/harder). Going forward, this becomes "how big of a corpus of this code is out there", because it impacts how proficient are likely to be at using 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.
รrdekes ez a 4, 2-es irodalmi, valamint programozรกsi hagyomรกny, amire Douglas Adams hรญvta fel a figyelmet, nรกlam ebbลl a hagyomรกnybรณl 4 a pszichiรกtriai, 2 a rehabilitรกciรณs tรฉma, ami รฉrdekes mรณdon maga is 4, 2-es, ami olyan, mintha rekurzรญv kezdene lenni, de mรฉgsem az teljesen www.textlog.hu/a-4-adel-es-2-szuzett/
This 4, 2 literary and programming tradition, which Douglas Adams drew attention to, is interesting. In my case, 4 of this tradition are psychiatric and 2 are rehabilitation topics, which is interestingly itself a 4, 2, which seems to be starting to be recursive, but it is not completely www.textlog.hu/a-4-adel-es-2-szuzett/



