We've had serious trouble with migration merges when two people work on different parts of the code, yet in the same module, and they both generate a "migration nr. 6" on their feature branches.
I put that word in quotes because I don't want to imply it's a problem - it's just something you need to know how to handle.
https://docs.djangoproject.com/en/5.1/topics/migrations/#ver...
You just rename one of the two files, and add the dependency. If they touch the same fields, you obviously have to resolve that manually.
This is the trap of the local maximum.
As opposed to what mentality ? I mean any tool I worked with has the same problem.
> > Everything is great, you just
Part of the python mentality is to pretend difficulties aren't there in order to keep presenting itself as beginner-friendly.