mikecaulley

3 ms·

1. 1.▲
   by mikecaulley 2y ago

   This doesn’t consider compute cost; the RAG model is much more efficient compared to infinite context length.
2. 2.▲
   by mikecaulley 3y ago

   I’m curious to hear what are some of the most frustrating points developing with Django, React, and GraphQL.
3. 3.▲
   by mikecaulley 3y ago

   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.
4. 4.▲
   by mikecaulley 3y ago

   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 to other entities.
5. 5.▲
   by mikecaulley 6y ago

   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 you optimize for only the most likely cases, the effor
6. 6.▲
   by mikecaulley 6y ago

   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 extremely similar. There are different things to look
7. 7.▲
   by mikecaulley 6y ago

   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 like GraphiQL make exploring APIs a pleasure. And rega
8. 8.▲
   by mikecaulley 6y ago

   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 libraries I wanted to gain some more experience wit
9. 9.▲
   Show HN: Teddy Bear Tracker iOS App

   18 points by mikecaulley 6y ago|5 comments