In all my professional experiences so far I've seen a lot of people/teams ignoring the meaning behind a Pull Request (PR), treating it like a kind of bureaucracy to deploy their piece of code.
Sometimes I heard people saying to each other: "I'll open a PR, just accept it because everything is fine". In the end that accepted PR crashed the entire system, I can say that reviewer was as wrong as the reviewee because he was negligent!
We can't automate everything, people think by using automated tests they don't have to do anything else to guarantee the code quality.
A few months ago I’ve started to contribute with returns, an amazing Open Source Python library with a lot of containers to help us in many ways, I won’t cover those containers here but you can access the documentation page to know more about them.
Here I’m going to cover why we chose the monkey patching technique to implements a feature, Improve Failure Traceability, to the Result containers.
Just a brief explanation of what is a Result container, basically your code can take two ways:
Software Engineer at @globocom. Passionate for challenges, technology, good code and functional programming enthusiast. @dry_py core developer