olistik boosted

Got a query this morning from DHS, asking about buying Sidekiq Enterprise.

My response:

"I can't morally justify selling to or supporting the DHS in any way, not while your organization is separating families and locking up kids."

olistik boosted

Today I finished listening to the Changelog episode about the journey that took Segment to come back to the mono-repo:

changelog.com/podcast/312

To me, the most interesting pain point about microservices they described is maintaining and evolving a shared library between the services.

Show thread
olistik boosted

"The code you write makes you a programmer. The code you delete makes you a good one. The code you don't have to write makes you a great one." - Mario Fusco

olistik boosted

@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:

dry-rb.org/gems/dry-monads/1.0

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: dry-rb.org/gems/dry-matcher/

olistik boosted

I'm looking for feedback 💬 over a small Ruby :ruby: implementation of the Result Object: source.olisti.co/snippets/1
Thanks in advance. 🖖

olistik boosted

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.

olistik boosted

I'm going to watch, once again, this beautiful keynote by Avdi Grimm:

youtu.be/-JpAUN6Ovok


I'm using Ruby professionally since 2006 and I'm not that good at introducing myself. 😄
Feel free to ping me to chat about *.

Ruby.social

A Mastodon instance for Rubyists & friends