I notice that language models are much better at programming than at writing. This is largely because, in programming, they have a closed feedback loop that allows them to find errors. Writing is much more complicated because the feedback is much more diffuse and delayed over time. In fact, it is often not well-defined.
Any conversation
kรฉsztetรฉst รฉrzek, hogy valami ilyesmivel (is) foglalkozzam, a kรณdolรกshoz egyelลre nincs agyam, de majd azt is szeretnรฉk, csak scripteket, semmi komoly programnyelv, de vรฉgรผlis a JavaScript is scriptnyelv
I feel the urge to do something like this, I don't have the brains for coding yet, but I would like to, just scripts, no serious programming languages, but after all, JavaScript is also a scripting language
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.
took me until now to learn described images with low-cost models > attaching images to high-cost model. silly me. output quality remains, cost lowers.
