How to smartly keep a set of Django ORM objects in order for drag-n-drop like situations.

ManyToManyFields confuse a lot of people. The way you relate objects to each other is just different enough from dealing with ForeignKeys and just uncommon enough in day-to-day Django development that it's easy to forget all the little tricks for dealing with them.

A very common pattern in a Django Project is to have some kind of 'model-type' relationship, where you have some kind of object that can only belong to one of the types defined in the database.

It is often necessary to differentiate between an argument that has not been provided, and an argument provided with the value `None`. For that purpose, we create what's called a 'sentinel value'.

In this post, you will learn how to create a Celery task inside a Django project in a Docker container. Sounds awesome, right?

django-test-plus has long been a useful helper library with Django. Now we've added some simple pytest fixture support to make it even more useful!

More and more often, we see schema designs that use UUIDs as primary keys. That's a valid choice if you're concerned about sharding and partitioning your database, but it has its own drawbacks, sometimes in unexpected places.

Ran into a weird error with coverage, pytest, and Travis today and wanted to document an easy fix when you get a 'import file mistmatch' error from pip packages you do not control.

easy-mode, cross-namespace object copy

Overcoming the read-only configMap with Helm