…t be afraid of super specific mutations that correspond exactly to an update that your UI can make. Specific mutations that correspond to semantic user actions are more powerful than general mutations. This is because specific mutations are easier for a UI developer to write, they can be optimized b…
Some teams, like the GraphQL team at Shopify, prefer to write names the other way around —
createUser. This is useful for schemas where you want to order the mutations alphabetically (the Ruby GraphQL gem always orders fields alphabetically) and your data model is mostly object-oriented with CRUD methods (create, read, update, and delete). When all your mutations are centered around a handful of object types this convention makes sense.
They don’t understand that I have a family to feed, mortgages to pay, deadlines to meet. They don’t realize that in order to make time for coffee, I would have to compensate for that lost time and stay up until 2 in the morning just to work.
Before reading the very first row, SQLiteCursor calls
getCount() for bounds checking. Since SQLite must scan the entire result set of a query to count it (again, like a linked list), this can add significant overhead. If you’re paging in a large query to a UI gradually, in response to the user scrolling, you may not…