Decorators and Separation of Concerns

Learn how decorators help achieve high cohesion and low coupling in software design.

We'll cover the following

Refactoring a decorator
- Separating the responsibilities of our decorator
- Combining decorators

We have already explored the idea of reusing code and noticed that a key element of reusing code is having components that are cohesive. This means that they should have the minimum level of responsibility—do one thing, one thing only, and do it well. The smaller our components, the more reusable they are, and the more they can be applied in a different context without carrying extra behavior that will cause coupling and dependencies, which will make the software rigid.

Refactoring a decorator

To explore what that means, let's revisit one of the decorators that we used in a previous example. We created a decorator that traced the execution of certain functions with code similar to the following:

Get hands-on with 1400+ tech skills courses.

Preface

Introduction to Clean Code, Code Formatting, and Tools

Pythonic Code

General Traits of Good Code

The SOLID Principles

Using Decorators to Improve Our Code

Getting More Out of Our Objects with Descriptors

Generators, Iterators, and Asynchronous Programming

Unit Testing and Refactoring

Common Design Patterns

Clean Architecture

Conclusion

Decorators and Separation of Concerns

Refactoring a decorator