Practical guides on Django, backend engineering, and building products that scale.
The pilot does not hand the controls to the co-pilot and go to sleep.
Model.save() never validates your choices. Here's how to make the database do it instead.
One method call decides whether Django asks the database once, or once per row.
Every log line, tied to the request that produced it, without threading request through your code.
No new dependencies, just Django's cache framework and a bit of arithmetic.
It looks like a fresh list every time you call it. It isn't.
A list remembers order. A set only remembers who's already in the room.
Share data across every template without repeating yourself.
Need someone who focuses on systems architecture and performance, leads a team, and still writes the code?