A common problem I see developers struggle with is passing extraneous data down functions where it doesn’t feel like it belongs as argument. It’s common to see this kind of thing happen when someone is eliminating global variables when refactoring, or when passing redundant data for performance reasons. Not much is written about this (anti-?) pattern. According to stack-overflow, this is called “tramp data”: The data itself is called “tramp data”.

Authorization is a simple problem with a very large and complex solution space. I’m going to plant a flag and say Django’s documentation on authorization follows a bad pattern (for most applications). Django’s built-in permissions work well enough for the django-admin views, but they’re not ideal for a generic web application. Django goes all-in on the “permissions-as-data” pattern. Every possible action is a permission object, and these permissions are linked to users or groups.

Make development easier by using local domain names during development

If apollo doesn’t yet support suspense, wrap it in react-query

Use generators to make python promises easier on the eyes

Color systems, schemes and productivity tips

3 tips to make django templates more pleasant

Embrace fat dataloaders, skinny resolvers