Theory reuse > code reuse almost every time.
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.
โฆ
NIH syndrome? I am guilty of it too. I love implementing things from scratch, you learn a lot by doing so and you get to own the codebase end-to-end, so no surprises and fighting around othersโ choices. It can get exhausting too though, in the end I succumb to using off-the-shelf components because my primary goals move at a higher level.
a constant, existential pull
so old I couldn't tell you the end
or draw its shape
between kind acceptance
and striving, struggling, writhing, climbing
learning, growing, discontent
"do you feel this way, too, at endless war with longing itself?"
but the birds and trees and ants and wind
in their own marvelous design
don't reply
we also launched Norma! :)
It checks AI-generated code for security, quality and maintainability while the agent is still working, rather than after a pull request opens. The output is deterministic. Here the demo link: portal.qualityclouds.ai/demo
I truly love the experience of using apps with rich, deeply interactive, beautifully animated, gorgeous user interfaces.
Then I see a beautiful text-based interface and something about it feels so natural, so inevitable, so perfectly clear, and I'm instantly captivated by its simplicity and clarity.
Hypertext is fascinating.

