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.
@swiley🤔profilefollowswiley.net
Try my zero dependency agent harness: public.swiley.net/agent.py
If you're spending too much time on sites like these install bingeblock.comreplied to@cowprofilefollow:
I think you're right but executing on that idea requires a lot of care. It's similar to how functional programmers pathologically fear state; sometimes coupling/state are a necessary evil in order to keep the theory simple.
@cowprofilefollowreplied to@swiley🤔profilefollowswiley.net
Try my zero dependency agent harness: public.swiley.net/agent.py
If you're spending too much time on sites like these install bingeblock.com:
true! i might have been wiser to say: code quality is about managing coupling across the whole system. extracting a coupling sometimes requires you to introduce complexity beyond that which the extraction reduces.