David Seddon, a senior developer in our team,
recently published an interested blog post on “The trouble with
transaction.atomic” drawing
on internal discussions within our tech team.
This was picked up by the core Django team and a new durable flag has already
been added to the django.db.transaction.atomic function — see the development
branch docs.
We can look forward to this feature in Django 3.2.
Would you like to help us build a better, greener and fairer future?
We're hiring smart people who are passionate about our mission.
- Building the largest electric vehicle smart-charging virtual power plant in the world
- How we ship over 100 versions a day to over 25 environments in more than 10 countries
- Avoiding race conditions using MySQL locks
- Estimating cost per dbt model in Databricks
- Automating secrets management with 1Password Connect
- Understanding how mypy follows imports
- Optimizing AWS streams consumer performance
- Sharing power updates using Amazon EventBridge Pipes
- Using formatters and linters to manage a large codebase
- Our pull request conventions
- Patterns of flakey Python tests
- Integrating Asana and GitHub
- Python interfaces a la Golang
- Beware changing the "related name" of a Django model field
- Our in-house coding conventions
- Recommended Django project structure
- Using a custom Sentry client
- Improving accessibility at Octopus Energy
- Django, ELB health checks and continuous delivery
- Organising styles for a React/Django hybrid
- Testing for missing migrations in Django
- Hello world, would you like to join us?