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
Nudged by an interesting read about time perception to try reclaim moments where I can deliberately feel bored again.
I've avoided social media (except YouTube) all my life, but this looks like it could finally be a better way to do it.
Maybe I'll keep a running journal of cool things I'm working on here or weird bugs that I've found. Or just the struggles of coding.
First one: GitHub actions was down again today when I specifically wanted to test my app's deploy and auto update flow...
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
Sharing a great read today:
Some of the takes are on the extreme end, but like most IT decisions, you can dial the pain to exactly what you want.
^C
textlog runs on a 2.5€/mo vps 1 core/2gb ram, using just one instance of Bun with its embedded SQLite. Works perfect and I run a few other apps as well on that machine.
