You Attended Talk: an introduction to event sourcing

For an "introduction" talk, it was pretty tech heavy, with a lot of code samples to try and process. Combined with barely being able to hear the speaker, I spent half the talk lost. Hopefully the recording will make the topic clearer.

interesting topic but would have benefited from real world examples showing impact on speed of application. example of how to then use the data would also help. Speaker himself suffered from the room not having a mic and noisy air con. looking forward to being able to check out the slides and sample code myself

The subject was really interesting, but it was really hard to concentrate on the talk and the slides. Some slides (especially with code) were handled pretty quickly while I could've used a bit more time to process what was in there. It didn't help that the room sound system was pretty much non-existant so it was hard to hear the speaker, plus it was really warm in the room, but that meant losing concentration too much and losing the story at some point about halfway.

Although the speaker had to put up with stifling heat in the room and no microphone, I thought he did a good job on (as his first conference talk) remaining relaxed and confident about the knowledge he was trying to put across. I thought he had spoken many times before. We went through the code slides rather fast and although I was able to keep up with what Chris was saying, I think others may have had a problem with keeping up to speed with the fast progression - I had never done anything with event sourcing before. I am looking forward to Chris's next talk.

- No microphone made it difficult to hear (not the speaker's fault)
- Perhaps a little more time could've been spent on the slides that were more complex code examples (-1)
- Clearly knowledgeable about the topic, presented really well, and handled some great questions at the end.

A good introduction to something I'd only heard of previously. As others have mentioned, I found the code samples hard to follow; in particular, it was hard to understand how they related back to the flowchart (which did make sense). There also seemed to be a lot of classes names 'BowlingGame' in different namespaces which made it less obvious what was going on.

I wonder if the code would be clearer by working through the flow chart, highlighting an element of it, showing the code, then back to the flow chart and the next element, then to the code etc.

It also got a bit much when you had half a dozen use statements - perhaps you could lose those, and use class names that describe what they do, rather than relying on the namespace (and then ugly shortened names to fit the class names on the slides).

It's good to see code in a talk like this; with some tweaking I think they would bring it alive a little more.

I enjoyed the talk it was very informative. I did find it a little difficult to follow the code but the rest of the talk was excellent.

The speaker a hard job with the room. microphone not working a loud aircon.

I will defiantly be discussing where using this technique at work.

The code examples were fairly hard to follow although I followed the principals fairly well.

It did not help that the room was extremely hot and that the microphone was only for the benefit of the cameras.

A great first look (for me) at the subject. The code samples given on slides were a little hard to follow but I'll be sure to checkout github later and figure it out there.

Good introduction to event sourcing. Would be interesting to see an example from the speaker with more of an emphasis on reading the data.

For an introductory talk it might have been a little code heavy.

Especially with it's specific broadway implementations. This meant that while looking at the code, you had to figure out how broadway did things and understand what message the speaker was trying to convey, sometimes in a very short timespan.

I did think the speaker as very knowledgeable about the subject and that showed in the talk.

Very knowledgeable, I learnt quite a lot as I only had a vague idea about event sourcing. Struggled to hear unfortunately which made it hard sometimes to keep up.
Some live code examples (or simulations ) would have been great to demonstrate the prices of collecting events, projecting them, then re-running them.