hey y'all! this is the first post!
Any conversation
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
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 find myself building bespoke tooling for my own and workflows these days, not only because of the obvious reason of software being so much cheaper to build, but also because there are SO MANY options for solving any given problem that it feels impossible to evaluate all of them.
If it's not a crucial piece of tech for a work problem then it often feels like paving my own way is both cheaper mentally (kind of amazing that's true these days) and probably a better fit.
The best Mcp server I have as Claude Connector is Emacs running on my Homeserver. It has one tool - eval-elisp. Using it Claude can do almost anything. My top 1 pinned chat is โRun agent-start-claude-code using HotterEmacs in dir โฆโ - after that I have a ready to use remote-controlled session running on my homeserver.
Economist Lant Pritchett describes shifts in ideas as silly, controversial, progressive, then obvious.
Also:
"Radio has no future. X-rays are clearly a hoax. The aeroplane is scientifically impossible." - Lord Kelvin
". No wireless. Less space than a nomad. Lame." - CmdrTaco

