i love indian food.
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 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.
ๆ
ไบ็ๅผๅคดๆปๆฏ่ฟๆ ท๏ผ้้ขๅ
ถไผ๏ผ็ไธๅ้ฒใๆ
ไบ็็ปๅฑๆปๆฏ่ฟๆ ท๏ผ่ฑๅผไธคๆต๏ผๅคฉๅไธๆนใ๏ผby ๅผ ๅไฝณ ใไปไฝ ็ๅ
จไธ็่ทฏ่ฟใ๏ผ
Stories always begin this way: a chance encounter, completely unexpected. Stories always end this way: two flowers bloom, then drift apart. (by Zhang Jiajia, I Belonged to You)
Looks like you-know-who has finally come for nitter. :-(
nitter.net
I gotta confess, I vibe codet a Kirigami-based application and I liked it. I am a anti AI person, and cannot wait for the bubble to burst. Yet I see it can empower people that do not know a tech stack, and get good enough results out of it. However i also see, it makes you lazy (and frustrates as soon as it gets somewhat complicated). It seems it is being adopted everywhere. This is scary... if it becomes necessary, will you be able to find a job where they don't require you to use AI?

