Trying tsoding/tatr idea for task tracking in the project. Instead of his C implementation asked CC to implement tatr.el. I do similar thing with vulpea, even my org notes have timestamp ids. Tatr tasks live in the repo, which is good.
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'd been listening to di.fm for years, and have been missing a MacOS app. Thanks, Antigravity, for making the world of personalized software really easy: fifteen minutes and two small bugs later, github.com/haykinson/difmplayer gives me a Spotify-style player. Yay!

