Very nice talk first part is good about Command patterns and they should be used, but later it deviate a lot from coding and different is way much to be used in normal environment. Also step adapter is good but it still deviate a lot from ruby coding.
This pattern shown at the beginning (pass config and collaborators to the initialiser, pass data to the call method) is exactly how I personally like to create service objects: it’s great and makes for straightforward testing and dependency injection. But it’s not the command pattern, as I understand it? My understanding of the command pattern is that it’s for a very specialised use case where you build an object with everything, including the data, and then execute it (with no arguments) later. The canonical example I’ve seen is of a text editor, where individual commands are created into an undo stack. But maybe there are competing definitions? Does anyone have a link describing the version of the command pattern described in this talk?
How is it working with multiple steps if each step is writing something into DB, it have something like ActiveRecord::Transaction? if some step fails it is not committing changes to db?
High level programming might not be understood by all that's for sure. Been using it at the highest level for three years now, let me tell you there is nothing clearer than this lib, and the paradigm dry introduces is probably the best one out there. Good luck to you.
This is pretty impressive and the result is "chef's kiss"
watching this makes me kinda regret not focusing on phoenix and elixir lol
Haha there things like this are much more simpler :)
Very nice talk first part is good about Command patterns and they should be used, but later it deviate a lot from coding and different is way much to be used in normal environment. Also step adapter is good but it still deviate a lot from ruby coding.
This pattern shown at the beginning (pass config and collaborators to the initialiser, pass data to the call method) is exactly how I personally like to create service objects: it’s great and makes for straightforward testing and dependency injection.
But it’s not the command pattern, as I understand it?
My understanding of the command pattern is that it’s for a very specialised use case where you build an object with everything, including the data, and then execute it (with no arguments) later.
The canonical example I’ve seen is of a text editor, where individual commands are created into an undo stack.
But maybe there are competing definitions?
Does anyone have a link describing the version of the command pattern described in this talk?
How is it working with multiple steps if each step is writing something into DB, it have something like ActiveRecord::Transaction? if some step fails it is not committing changes to db?
Thank you! On my way to increase my salary!
I don’t like this lib! It’s just complicating things that we already have in the core language and complicate things more…
High level programming might not be understood by all that's for sure. Been using it at the highest level for three years now, let me tell you there is nothing clearer than this lib, and the paradigm dry introduces is probably the best one out there. Good luck to you.
it just takes some time to get used to idea of functional programming, it helps a lot once you on with the idea.
As much as I feel like this will take a while to fully understand, it sounds like it might br worth it.