We are currently releasing older YOW! videos to serve as a valuable archive, preserving historical content. It is possible that a video is perceived as outdated. We believe it offers insightful glimpses into the past, enriching our understanding of history and development.
For those that liked his ideas on intuition and those that didn’t, you may like to read “Focusing” or “Thinking at the Edges” both written by Eugene Gendlin.
I'm not sure if swapping between MVC and Pub/Sub really proves the point. Pub/Sub is just the natural pattern for the example given. So it feels like just swapping one pattern for the other to get the correct recipe. The content was all very good though. It's very difficult to explain that after you've learned the rules of the game, you have to learn to play the game. I'm not sure I could've given an example of that without showing that if you have the correct mindset, you'll naturally come to better patterns than if you went looking for patterns at the start.
Whoever crossed their path with functional programming knows that the passing parameter paradigm has its flaws. E.g. when the data originates in a higher stack from when its needed you have to pass it down at every function call. That means even functions in the middle has to take the parameter in order to pass it down. One new parameter required in a less abstract function requires a chain of updates in all the functions in the middle. This is annoying and that's why Web Applications pass down a single gigantic Request data structure with any data that might be required at every level of abstraction that needs to deal with a Request context. I'm ok with message passing, but when the message contains all the state it's disturbing (i'm thinking of lenses, pattern matching, and the likes just to distill what I need from what the whole application need). If we add that in functional programming data is passed by value...
![[Full] 4 ต่อ 4 Celebrity EP.910 | 22 ก.ย. 67 | one31](http://i.ytimg.com/vi/4TR3MVpOiw8/mqdefault.jpg)
We are currently releasing older YOW! videos to serve as a valuable archive, preserving historical content. It is possible that a video is perceived as outdated. We believe it offers insightful glimpses into the past, enriching our understanding of history and development.
Excellent talk
For those that liked his ideas on intuition and those that didn’t, you may like to read “Focusing” or “Thinking at the Edges” both written by Eugene Gendlin.
Love it!
I'm not sure if swapping between MVC and Pub/Sub really proves the point. Pub/Sub is just the natural pattern for the example given. So it feels like just swapping one pattern for the other to get the correct recipe.
The content was all very good though. It's very difficult to explain that after you've learned the rules of the game, you have to learn to play the game. I'm not sure I could've given an example of that without showing that if you have the correct mindset, you'll naturally come to better patterns than if you went looking for patterns at the start.
Nice talk
Whoever crossed their path with functional programming knows that the passing parameter paradigm has its flaws. E.g. when the data originates in a higher stack from when its needed you have to pass it down at every function call. That means even functions in the middle has to take the parameter in order to pass it down. One new parameter required in a less abstract function requires a chain of updates in all the functions in the middle. This is annoying and that's why Web Applications pass down a single gigantic Request data structure with any data that might be required at every level of abstraction that needs to deal with a Request context. I'm ok with message passing, but when the message contains all the state it's disturbing (i'm thinking of lenses, pattern matching, and the likes just to distill what I need from what the whole application need). If we add that in functional programming data is passed by value...