89
Any conversation
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.
I still don't get how now after AI coding there's people saying that contrary to common belief code wasn't a bottleneck and I realized that when I was starting to code at 10yrs ago when I was 15 and read it in a stackoverflow comment. I thought that was the common belief and still can't believe a lot of supposed senior programmers apparently believed so.
I gotta confess, I vibe codet a Kirigami-based application and I liked it. I am a anti AI person, and cannot wait for the bubble to burst. Yet I see it can empower people that do not know a tech stack, and get good enough results out of it. However i also see, it makes you lazy (and frustrates as soon as it gets somewhat complicated). It seems it is being adopted everywhere. This is scary... if it becomes necessary, will you be able to find a job where they don't require you to use AI?



