A Series of Fortunate Events


Comments are closed.

Perhaps a little too Symfony-focused, with only a tacit nod to indicate that other frameworks also support Event Dispatchers using CoR; but an interesting introduction to event handlers in general, without being too lightweight.... and just a couple of wake-up slides to keep the audience interested

There was a good build up from simple event handlers to more complex ones. I also liked the concerns part of the presentation, because knowing the downsides of something is just as important as knowing the upsides. I'm looking forwards to reading your book.

Nice work reworking the code. That was insightful refactoring, which is directly applicable.

Very nice, loved the step by step improvements that took an example from bad to good.

Concept of events was explained nicely. Loved the incremental code refactoring from coupled one, graphics really helped break the code slides and make whole thing more understandable.

Get more colors!

Rated 4

Anonymous at 15:37 on 25 Jan 2015

Like said before, the incremental refactoring was really interesting and helpful.

The title really appealed to me as I'm as of late interested in events as used in event sourcing. This was not really in the scope of this talk, I realized, but maybe it's nice to incorporate some concepts of this in a 'further reading' section in the talk. So here I go :)

Maybe you could be more explicit in defining the difference between a command and an event. And explain how an event can trigger a whole chain of changes. Maybe even see the user as an event generator and the system as completely event driven. Although this might be too far fetched :)

And, if you could find time in the presentation, you could maybe gloss over a way of distributing events from one piece of software to another (from a PHP application which receives the initial command over to a NodeJS application which receives the events generated by that command, and then generates events locally in the JS application, for example), effectively crossing the application boundary. And beyond that maybe cross the machine boundary.
I think this would tie in nicely with micro-services and scaling applications.

Event sourcing and CQRS are out of the scope of this introduction to events, conceptual refactoring and loose coupling. But with these additions, I think it, should be a good primer for future talks.

The slides showed good insight of properly refactoring coupled code to event driven code. The question opportunities in between the sections were good (even though none were asked).

This talk is an introduction to harnessing the power of a mediator, and for that purpose it was great.

Well presented, good content. Good introduction in the topic.

Also enjoyed the Symfony-bashing (for the record: I'm a Symfony user myself).

It is obvious that Matthias knows his stuff, but I was not fully convinced by this talk on events. As pointed out in other reviews, the incremental refactoring was a nice touch, but the Symfony bashing seemed out of place and I did not find it to add much. Unfortunately, the talk did not really make me feel the power that properly implemented events can bring, it could perhaps do with making it a bit more focused. (single responsibility ;-)) I did enjoy the design principles party and the IoC plug.

Overal a good talk with a gentle introduction to the observer pattern. It was also nice to see that there were some good SOLID practices used in getting to the end result.

Described every aspect of events in a very clear way!

Matthias has a great way of teaching principles of software design. I'd definitely recommend this talk if you are wanting to find out the best way to write your own event system or better utilize a third-party event system.

Very nice step by step refactoring towards a great event based system. Also nice to see both the up and the downsides.