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
Sigh. On the heels of , I just went into our garage to find a panel of insulation fallen to the ground, riddled with mouse droppings. ๐คข๐ซ
Cleaned it up (gloved and masked, naturally), but probably means we need to re-insulate the whole garage. Which will undoubtedly uncover a leak or some other issue. The fun never ends!
"200K lines is not 10 times as much as 20K lines - from the mission perspective it's just irrelevant. And yet it's the easiest thing to measure. And so we look for the keys under the lamp post." ~Kent Beck
www.youtube.com/watch?v=F8fBgDCf2Y4&t=2753s

