[phn]

I mostly agree with other commenters, but I really must hard disagree with point 5.

Proper abstraction is the one thing you need to get right, and django makes it so easy to make clean separate modules work together using a shared base and way of working (user model, groups, permissions, urls, signals, etc.).

One day you'll need to use your payments logic to sell something else, embrace it.

[hsbauauvhabzb]

I wish the tutorial really explored this more. I’ve got some apps which have clear boundaries, but could be split into distinctive modules but I don’t see much value in doing so. I’d love to see an official example of this.

[jmconfuzeus]

If my payment logic is getting too coupled, I can easily extract it because I use one migration file per model and separate code using regular Python packages.

I can easily extract the logic into it's own app if I need to publish it to PyPi for others to enjoy as well.

Of course, if you code is getting coupled, then you need to revise your design process.