One of the powerful design patterns that can be employed within a GraphQL schema is the co…
Try as we might to design APIs that last, it is very difficult to completely avoid the nee…
tRPC has a fairly comprehensive set of built-in error codes, but because they’re baked in …
At Crimson one of the first projects undertaken by my AI team was to produce high-quality …
Design consistency is important, because it frees up developer brainpower for important wo…
One of GraphQL’s limitations is that it has no native concept of namespaces. All types def…
Can you spot the hidden findMany query lurking inside this GraphQL schema?
findMany
There are a few languages out there which come with multiple “types” of object, but GraphQ…
A major difference that delineates software from other engineering disciplines is the frag…
Aggressively nesting your GraphQL schema wherever possible is one of the best tools you ha…
If you started your programming journey in the early 2010s like I did, then it’s likely th…
On December 27, Crimson Education’s usage of GPT-4 doubled overnight and remained elevated…
We had an issue the other month with our internal summarization microservice, which necess…
Imagine that you’re building out a web page that allows students to view a list of their a…
Last year Retool authored a post describing how they upgraded a 4 TB PostgreSQL database f…
GraphQL schema design is hard, and a lot of engineering teams end up making mistakes when …
I previously wrote about my preferred ID format consisting of a small type prefix and a KS…
There’s a big difference between building with GraphQL and older style REST endpoints: Gra…
IDs are an essential part of API design. So much of the code we write as engineers uses ID…
Deprecating API endpoints has always been painful because there’s no ‘one true way’ to do …