About Using Signals Wisely

When you have complete control over the architectural decisions in your project, avoid using signals.

Instead, if you need to perform actions when a model is saved, handle this in the view or the form's save() method. This approach makes the logic clear and easy to follow, ensuring that all many-to-many relationships are properly saved.

Use signals only when creating an open-source, reusable app or framework. In such cases, signals are useful for tasks like model introspection, profiling, or logging.