@CharlesTingler pretty straight forward, personally I wouldn’t include temple system. I interpret it as the old covenant as the thing that passed away. maybe that’s what you meant ?
Coding agents expose a hard truth about evolution: optimization does not converge on what’s good, only on what survives the pressures we define.
@LangChain
My Nest fire alarm expired. Apparently they don’t make them anymore. It’s beeping very loudly once a minute. It’s 20ft up on my ceiling.
I am very very annoyed right now.
Naming your variables MyClass, MyObject, and doThing() probably boosts AI coding performance by like 37%… just matching its training data 😅
Can someone confirm? @karpathy
Using a sub-agent in #langchain feels a lot like spawning a subprocess in Python.
synchronizing state or memory between them becomes an interprocess communication problem.
That’s why the #deepagents instructions matter so much—they are basically the IPC layer for agents.
@davis7 is rxjs a good fit?
use Observables to orchestrate the HTTP stream (fetch → compose → transform), then bridge to an async iterator when you need pull semantics. Rx for flow control, for await for chunk-by-chunk iteration. Push core, pull at the edge.
lately i’ve been trying to map knowledge ai to physical ai and i keep coming up with weird conclusion like:
teachers might be the new software engineers
imagine the robotic equivalent of a phys therapist teaching them to interact with human world 🤨