I'm working on a +500k loc Django codebase that is a single app (but really should be 20-50 apps). It's a pain in the ass to work with. It is turning an alread

I'm working on a +500k loc Django codebase that is a single app (but really should be 20-50 apps). It's a pain in the ass to work with. It is turning an already complex monolith into a more complex monolith. New developers that join, struggle pretty much forever. Often leave, citing the uncessary complexity. Everything is "legacy" (this project started with Django 1.4), so using new tests, approaching code in a new way is out of the question, unless you wan't to refactor all the code. Perhaps it's a organizational issue, but its definitely one of the biggest points of frustrations. They absolutely do have a point when it comes to the positives of using one "app". But the well meant advice of being careful, doing this or that to avoid the problems named above; unfortunately don't scale (at least from my experience). If I am ever tasked to take over a Django codebase that is a single app, instead of lets say 5-10. My first priority will be to break this up in smaller apps before actually doing any actual work.