Trying tsoding/tatr idea for task tracking in the project. Instead of his C implementation asked CC to implement tatr.el. I do similar thing with vulpea, even my org notes have timestamp ids. Tatr tasks live in the repo, which is good.
Any conversation
signals. thinking about shifting my mental framework to identify signals instead of waiting for concepts to be assembled. exploring the amount of energy and opportunities for distractions through the operations of processing what just happened and what is happening to short circuit latent and unnecessary systems. cut through the assembly processes and identify the raw signals. recognizing that naming these "raw signals" is misleading. maybe, shifting observability lower in the stack.
Spotted this Royal Air Force A400 over the lake yesterday, it was so different from civil planes www.planespotters.net/โฆ/zm420-royal-air-force-โฆatlas-c1-a400m-180
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.

