Join 📚 Josh Beckman's Highlights
A batch of the best highlights from what Josh's read, .
The generation of a cache key is always important, but even more so with GraphQL. The dynamic nature of GraphQL queries is such that even a white space in the query could affect the key and cause a miss, even though it was the same query in the first place. A good cache key should generally contain at least:
User information (if authenticated API).
A query hash, which should be normalized as much as possible.
The variables hash (we would not want queries with different variables to be cached as the same thing).
The operation name
A cache-busting element.
Production Ready GraphQL
Marc-Andre Giroux
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
I used to tell people to look around the room you’re sitting in. Look at everything. Every noun. It almost all exists because a person willed it into existence. Nothing is stopping you from doing the same.
I see people online all the time dismissing someone else’s success because “I had that idea first” or whatever. I mean… yeah? If so then the difference is… you. So a bit of a self own whenever I hear that.
I can’t stress enough how little an idea matters compared...
Mitchell Hashimoto
...catch up on these, and many more highlights
Readwise