Viewing profile — mikecaulley

This doesn’t consider compute cost; the RAG model is much more efficient compared to infinite context length.

I’m curious to hear what are some of the most frustrating points developing with Django, React, and GraphQL.

Thanks for the great comment. I often see GraphQL get a bad rap in comments on this site but most of the time it seems to come from a misunderstanding of how to use it.

How you model the data at rest does not need to match the GraphQL specification. The GraphQL specification should be similar to your REST entities but they have traversable edges t…

Of course, you are building something that is much more powerful. If you intend every possible GraphQL operation to perform perfectly, it'll take more development effort. Though if…

Generally speaking, it's not more difficult than creating a REST API controller. Rather than mapping your service code to a controller, you map it to a (GraphQL) resolver. It feels…

I've found GraphQL to greatly improve the developer experience when building web apps. As a front-end developer you can easily get a full view of the data and relationships. Tools …

Let me look into what effort it would take to clean up the code and put it on Github. I'd be happy if it helped others starting a project. It heavily utilizes ReSwift and SnapKit, …

Two weeks ago when walking around my neighborhood I noticed a strange amount of teddy bears placed in the windows of homes. When I got home I searched the internet and found https:…