ismaelct
Joined 11 years ago
Karma
37
Submissions
28
Member since
Sep 30
Recent submissions
Comment · 2 years ago
Very nice
Comment · 2 years ago
I understand the sentiment but I think it's highly dependent on context. Where you work at, who you work with, org size, what the problem is, the cost and benefits of each abstraction, etc etc. I think it's our job as developers to put all those things on the scales when deciding what abstractions to use or not use. Whether a pattern is "the default" or familiar is certainly a big factor, but not the only one.
Comment · 2 years ago
What do you think of Ruby's built-in function composition? https://ruby-doc.org/3.2.2/Proc.html#method-i-3E-3E
Comment · 2 years ago
To be clear this is not a library. I'm just describing a pattern and a bare-bones implementation.
Comment · 2 years ago
Well spotted. Fixed. Thank you!
Comment · 2 years ago
Nice. Yes the pattern I describe in the article supports any callable too. I should point out that this is not a specific library, just a very bare-bones pattern.
Comment · 2 years ago
> If all those steps in your pipeline are defined in the same codebase
I find that rule a bit arbitrary. For example, I have data-import pipelines where some steps are unique to each task, but some others are shared across tasks. Why does it matter whether the steps are defined in the same codebase or not?
Comment · 2 years ago
I just wanted to make the either/or pun.
Comment · 2 years ago
Thanks Mitchell (big fan, btw!).
Indeed!https://github.com/hashicorp/vagrant/blob/main/lib/vagrant/a...
Yes, it's not a new pattern by any means, and there's many ways to "halt" the pipeline as you say. For example ActiveRecord stops callback chains if any callback throws ":halt".
Other examples are Redis.rb's pipelining API https://github.com/redis/redis-rb?tab=readme-ov-file#pipelin...
Or more generally any builder-style pattern that composes a set of operations for later execution, including again ActiveRecord's query chaining.
In my article I tried to show a specific implementation using the Railway pattern (where the result must only respond to "#continue?() => Boolean")
Comment · 2 years ago
Odd to see ROP and monads as an either/or problem (see what I did there?). Most ROP implementations I've seen rely on the result monad.
Comment · 2 years ago
I'm so going to steal this
Comment · 2 years ago
Good observations, thank you. I take the point about properly delimiting the boundaries of the orchestration layer in a system.
I think you're right about how that line comes across, I'll try and improve it.