As I said in recent other questions, the CMS we're developing at work is becoming a huge mess that's getting everybody lost (we started joking about not caring about it anymore with some coworkers...) I have been interested by the DDD for a quite a while now, and I am already testing it out myself on a personnal project (with experts friends). So far, things are ok !I founded out that DDD provides really interesting guidelines and concepts. As I am being more and more frustrated by our CMS code base, I am recently spending lots of time thinking on how to fix things up or help stirring the project to a saner horizon. DDD suddenly sprung into my mind as a potential solution to help us. We lack specifications, documentations, naming conventions, well defined architecture... barely everything vital to a huge project !I guess ubiquitous language, bounded contexts, aggregate root all are concepts that can provide some help even though the project's already started and not with DDD in mind... Moreover, we use Python, and I sincerely feel like using Python on huge project requires even more to pay attention to what we are doing. DDD could maybe provide us some tools for fixing our design...What would be right steps for ensuring we could sanitize the way we're working without ending up with even more mess ? Could something else than DDD provides more help to get us back on the right track ?
Getting a free-wheeling project ont the right track... DDD?
refactoring;domain driven design