Talk in English - US at ZendCon 2015
View Slides: https://speakerdeck.com/willroth/fear-not-the-machine-of-state
Short URL: https://joind.in/talk/cc72e
(QR-Code (opens in new window))
Fear Not the Machine of State!
Comments are closed.
Worth waiting for the projector tech support. Very useful.
I wish there hadn't been issues at the beginning so that the ending didn't have to be rushed a bit but it was worth the wait to get all the technical projector and font issues sorted out. @coderabbi handled the snafu's like a pro and when it was all back working presented without appearing to be rattled at all. Information provided was very valuable and informative. Without the glitches, it seemed like it would have timed out well and left a bit of time for a few questions. Overall though, one of the best I've seen this year.
This talk was about the state pattern which I hadn't really considered useful until this talk. Several different approaches were highlighted with one seemingly simple example analyzed in detail. Creating behavioral types that represent a state and it's transitions was shown to be a powerfully effective mans to adapt to changing requirements. The speaker was very easy to understand and follow, engaging and interesting.
Need the slides, badly!
I learned so much from this talk, it was great! Was a completely new concept for me, but he provided several great examples of code smells that indicate you should use the State Pattern, and I could immediately see where in my project it would help. Great job!
Good examples as a general illustration of the concept, but perhaps could you also devise an example that illustrates the stateless nature of http and the req/response cycle and how to reconstitute state? Otherwise, I found myself thinking about ways I could use this pattern in my work throughout the talk and that's great.
I wish I could sit in on every talk you give, this was really good and I look forward to the next conference.
Awesome presentation. Great humor and fantastic examples. I never would have imagined you could keep it so simple with some advance planning and refactoring.