Very nice talk about his experiences and how he started this career. Very entertaining!
A great and simple idea on having side projects.
Thanks Robert for an exellent example of the use of ddd in a real world example
Nicely done!
Content very useful, great presenters. But the framework did not move me much.
I think it was very good and worth traveling here from far. I would recommend however to have some theory section well demarcated to display some code examples as guidelines, they have to be simple enough to be interluded in less than 30 seconds but that can give insight to all groups per equal what would it look like to go down a certain path.
The invitation of the other 2 participants was a very good idea. Maybe an improvement would be to know when someone will or will not speak so that the flow is more continuous, though overall it was a very good insight from all fronts non stop which is superb.
Thanks! great workshop! I hope now I am a certified DDD-event-storming Engineer ^_^
Intresting talk also seen a lot.
Just the part about forms whas a speed rush where 90 % -> 100 of the people could not follow anymore.
Also te speed rush wasnt that much needed because the other talks went on until 17:00 and we stopped at 16:45.
lso a thank to Evan for the issue fix with the current.
Also a thanks to EvanDotPro for helping (didn't help me but still).
Also not there fault but just like Evan mentioned a micro should have ben nice.
Great workshop, glad I attended! Having Mr Brandolini there was a really nice addition, his insights about the whole process helped me a lot.
A few points (well actually it boils down to one major point) that would improve the training for me:
For me, near the end of the session it got the most interesting and felt we were cut short there. Had the feeling we followed the trail from scratch to code for about three fourths, which was a bit frustrating. Stijn explained me with a nice UML diagram what the flow would be of a command being processed in a CQRS system, these five minutes were worth a lot and boosted my understanding of how one would implement all that stuff. I would do more of that, in a structured way in front of everyone, instead of waiting for a student to ask about it and quickly explain it in person.
It's an event storming workshop so naturally there is a focus on the actual event storming, but the event storming itself isn't worth all that much if you don't know how to turn the mental model of commands, events and business rules into working code. That's why I would keep the event storming exercise a bit shorter (after two hours you get the point) and move on to the rest faster, allowing more time at the end to get into some implementation details. As always, a good example is worth a 1000 (I actually think a lot more than 1000) words.
You train people who code for a living. I am confident pretty much everyone in the room was left wondering how to take the car rental example further, into the realm of the pragmatic. So I think choosing just one of the cases that comes out of the modelling session and take an hour to turn it into pseudo code would boost the value of the workshop enormously.
All in all, well worth it! Thanks!