Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

README: add example of how *not* using Dispatch is a problem #107

Open
achille-roussel opened this issue Mar 4, 2024 · 0 comments
Open
Labels
documentation Improvements or additions to documentation

Comments

@achille-roussel
Copy link
Contributor

achille-roussel commented Mar 4, 2024

This issue is a follow-up to the feedback we got on the Python SDK, in particular:

The other thing I would try to do would be starting with an example of how not using Dispatch would be problematic and error prone, and explain "this would raise an error, the program would die, or you would have to write 50 extra lines of code to handle retries". And then, at that point, when I see what is the obvious problem, introduce Dispatch to the rescue.

We got this suggestion multiple times, since it can be difficult for someone first exposed to Dispatch to grasp the full breadth of value they can get from the product, putting it in opposition to the pain points that exist today can go a long way in to bridge the gap.

@Pryz Pryz added the documentation Improvements or additions to documentation label Mar 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants