Post

Clearing out tabs (4): Different way to store memory. Instead of chat history being linear, make it hierarchical, branched by summaries. It purports to work well. I haven't tried it yet. gist.github.com/VictorTaeli...

Haven't tried it, but I need to swing back to working the search feature. This library is for deep memory search for agents over large datasets. If someone tries it and can give a review, I'd love that. github.com/elstongun/l...

I found this on some thread where people were making fun of using specs for agentic coding. Even though I write specs with agents, this is rather similar to how I think I'm working: exploring the state space and design space. registerspill.thorstenball.com/p/building-...

So then my question: do you actually need the implementation to come to the same conclusions? Before agents, it was unequivocally yes. Now, I'm not so sure. Some things you can get away simulating with the agent, or build a prototype without the impl. What are the conditions?

Dan Wang's 2025 was a nice, if long read, mostly on the US, China, Europe comparisons on the industrial base and AI. It takes mostly a fair stab at each, and is a nice broad overview. However, I'm unclear what my own takeaway is, other than ambience. danwang.co/2025-letter/

Let's be specific about what spec-driven dev is. I write a spec with an agent. But the spec is small enough to iterate, big enough to take advantage of how fast agents are and one-shot the feature. www.youtube.com/watch?v=F8f...

I also don't sync the specs. I keep an append-only log of specs, just like RFCs. How I work isn't waterfall (what Kent is thinking), nor is it what people commonly refer to now as Spec-driven. But I do agree what's important is the learning and understanding.

I disagree in that you can't learn and explore the state and design space at the spec writing phase. You can't explore every nook and cranny, it's not a silver bullet. But you can learn a surprising amount you couldn't before!

An interactive explainer on simple predictors. It makes me wonder how branch predictors in CPUs work, and if they're anything like this....and apparently, they already are n-gram predictors! (but they don't do backoff, presumably due to latency requirements) aaronsonoracle.com/