Join 📚 Josh Beckman's Highlights
A batch of the best highlights from what Josh's read, .
It eventually got bulldozed by multiple attempts of normalizing over Go practices, which essentially leave you on your own whenever it comes to operational aspects of the development cycle, and then containerization took over and the whole pipeline was voided of ways to do the nice stateful thing that saves everyone hours of rollouts and draining and reconnection storms with state losses.
A Pipeline Made of Airbags
ferd.ca
Persisted queries are a must for all internal APIs, and I suspect they might become useful for public APIs as well eventually.
Production Ready GraphQL
Marc-Andre Giroux
My gut tells me this pattern, which doesn’t really have a name, is going to be *the* pattern for working with these technologies to do complex things. The best name I can find for it is “specification repair”—see, for example, [this paper](https://arxiv.org/html/2309.16120v3). You ask a question and the LLM transforms it into a more detailed specification of a problem, then writes code to test that specification, then creates more specification, then tests that.
Is “Specification Repair” the AI Endgame?
Paul Ford
...catch up on these, and many more highlights
Readwise