Join 📚 Josh Beckman's Highlights
A batch of the best highlights from what Josh's read, .
It’s also silly when the moral terms of our engagement with other people are set for us by the discourse, whatever that is. And, I mean, on my less generous days, I go with it just like anyone else. The same as ordering a Lyft or ordering a hamburger because I don’t want to cook. The convenience of our moment recreated in not just our art but also our human discourse and human congress.
Massachusetts Holy Ghost - By Brandon - Sweater Weather
blgtylr.substack.com
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
We all bring cognitive biases. The explicit ones we love to cast as “experience,” and the implicit ones go unacknowledged.
Good Decision-Making Is Good Process
Ilya Grigorik
...catch up on these, and many more highlights
Readwise