Problem solving:
Two steps forward, two steps forward, two steps forward...
Coyote, look down.
Any conversation
I've been enjoying toast to help click through a project. I still mostly use Zed to handwrite code, but it's nice to open a pane and fire up toast from the terminal. paradise-runner.github.io/toast/
At moms house for the holiday weekend so the kids can see Nana. She has a "premium Plex" account on her tv serving a truly massive amount of content. Allegedly the brother of a long time friend is offering the "service". She says that the service will go down when the host is having outages, so the infra is likely local.
I brought my year this weekend. We are going to dig in to this guys operation. Intuition dictates that there is some hand rolled accounting going on. I'd like to see it.
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.
A thing I've been doing lately is trying to come to the same conclusions others have without looking their the direct techniques and code. Last night I tried to figure out why people do vector based retrieval for RAG and ended up running these experiments: n0tls.com/โฆ/2026-09-03-i-think-โฆrag-with-grep.html
I'm still going to do an explore agent.


