/explore
|
You are here 
|
florimond.dev | ||
| | | | |
martinheinz.dev
Even if you write clear and readable code, even if you cover your code with tests, even if you are very experienced developer, weird bugs will inevitab... |
|
| | | | | ||
| | | | |
jimpurbrick.com
[AI summary] The article discusses the use of Python decorators for handling web requests, their interaction with introspection, and methods to preserve function metadata while maintaining decorator visibility. |
|
| | | | | ||
| | | | |
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. |
|
| | | | | ||
| | | | |
sookocheff.com
I previously talked about what functional programming is by comparing it to other programming paradigms. This post expands on that post to talk specifically about practical differences between functional programming and the paradigm most of us are intimately familiar with - imperative. This post is punctuated with some quotes from the book An Introduction to Functional Programming Through Lambda Calculus. It's worth noting that each of these practical differences are enabled because of the power of referential transparency. |
|
| | | |||
