Today I finished listening to the Changelog episode about the journey that took Segment to come back to the mono-repo:
To me, the most interesting pain point about microservices they described is maintaining and evolving a shared library between the services.
@olistik About this
> from the documentation of dry-rb/monads I cannot see how different kind of Success/Failure can be handled.
If I got this question right, the construct for cases are kind of different:
The main idea is to use Results mixin and later apply Matchers to the payload.
But matchers are their own beast. IMO mixing with Results would make more complicated. That's why there's a dry-rb/matchers: https://dry-rb.org/gems/dry-matcher/
I wrote up some heartfelt words about why I left Twitter: https://medium.com/@thomasfuchs/good-riddance-twitter-a572bdf0fb73
Please share it if you agree. Thank you.
I'm looking for feedback 💬 over a small Ruby implementation of the Result Object: https://source.olisti.co/snippets/1
Thanks in advance. 🖖
Learned Ruby in 2005 coming from Python, built a number of applications during the years, enjoyed almost all of them 🐵
These days I do lots of Elm, and pretty soon will start dabbling with Elixir again.
I also do DevOps.
All these hats will kill me.
Play Low Mem Sky, a chill game inspired by No Man's Sky | PC Gamer https://www.pcgamer.com/play-low-mem-sky-a-chill-game-inspired-by-no-mans-sky/