|
You are here |
bfontaine.net | ||
| | | | |
juandebravo.com
|
|
| | | | | Juan de Bravo - Personal thoughts about technology (@juandebravo) | |
| | | | |
blog.meadsteve.dev
|
|
| | | | | Why I would default to choosing sequence over list when adding types to a function | |
| | | | |
www.alexstrick.com
|
|
| | | | | ||
| | | | |
blog.nuculabs.de
|
|
| | | Hello, In this short article I would like to talk about context managers. I personally consider that at the core they are just a form of decorators. If you don't know what a decorator is check the Decorator Pattern Wikipedia article. Decorators can be used to implement cross-cutting concerns. We have componentA and we need logging and security, we could write the logic for logging and security handling in componentA but some people consider component a should be componentA not componentAthatAlsoKnowsAboutSecurityAndOtherStuff. Since it's not the component's responsibility to authorize requests or log calls to a external logging service, we can wrap the componentA into a decorator that does just that. | ||