good morning everyone, drinking coffee with syrniki and strawberries.
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.
been building a voice first os using jev and some small voice models. I'm surprised how well it's working and I'm very close to the point where I can go into a feedback mode and tell it what behavior I want changed, it will spin up Claude or codex inside itself and setup the build to restart itself and continue with new code. tempted to let it build itself completely
How do you define slop in relation to ? For me, it is how quickly you get to an unmaintainable state- the acceleration into something that becomes difficult to work. I talk more about it here: hellodavid.dev/blog/slop
ive been rocking my thinkpad 460s since 2018 or so, but ive just recently yolo purchased a chunky t420 for 80โฌ. I gotta say this is the best laptop ive ever used, keyboard/io is unmatched and it still runs super snappy on omarchy right now, even with only 4 gigs of ram :D AND this thing has a cd drive!






