It's always worth reading Against Railway-Oriented Programming[1] before you commit to using it.

Personally I've dealt with enough Trailblazer code now that for business logic I think I'd much rather work with a simple ruby class with a procedural interface.

I like the use of a Result object but not at the expense of exception handling or bloated stacktraces full of library code.

Being lightweight, easy to debug and upgrade is underrated IMHO.

Having said all that, I still think this is a really interesting article and great food for thought depending the usecase.

1. https://fsharpforfunandprofit.com/posts/against-railway-orie...