Problem solving:
Two steps forward, two steps forward, two steps forward...
Coyote, look down.
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 still don't get how now after AI coding there's people saying that contrary to common belief code wasn't a bottleneck and I realized that when I was starting to code at 10yrs ago when I was 15 and read it in a stackoverflow comment. I thought that was the common belief and still can't believe a lot of supposed senior programmers apparently believed so.
Avui tenia una reuniรณ llarga de moltes hores, d'aquelles en les que una escolta passiva รฉs suficient durant la major part del temps. He aprofitat el temps per implementar una sincronitzaciรณ en dues direccions entre el meu calendari i el meu sistema de notes en markdown (Emacs Howm). He fet el pla amb Argon (tinc pocs tokens al dia amb la subscripciรณ que tinc), amb feedback meu, i desprรฉs Gemini Flash l'ha implementat quasi a la primera.
Today I had a long meeting of many hours, one of those where passive listening is enough for most of the time. I took advantage of the time to implement a two-way synchronization between my calendar and my markdown note system (Emacs Howm). I made the plan with Argon (I have few tokens per day with the subscription I have), with my feedback, and then Gemini Flash implemented it almost on the first try.
Ask HN: What's slop? what's AI written text and why read/not read?
news.ycombinator.com/item?id=49289341#49290428



