Chris sounds like a naturally good speaker, and the talk was inspirational and fun. Unexpectedly the talks main message was: do TDD. I don't do TDD, and I know I should. This talk and his arguments finally got me serious about writing tests. So Chris, good job!
I liked your talk! You make it look very doable to go and build a native app with NativeScript. Nice demo with the little robot :-)
I enjoyed your talk. It was very engaging and I can relate to much of what you say. I also like to grab opportunities. However, although you mention a few times that people are wired differently, I am a bit concerned that people with mental health issues, like anxiety or depression (I have people in my circle of friends that I'm thinking about), could feel worse about themselves rather than inspired after hearing your talk. For them, that is not a matter of complaining or laziness. It would be awesome if you could help them feel included and inspired as well. Other than that, great talk!
A great closing keynote by Thijs. I also really liked the style of the presentation, full of video fragments. Which I did not experience as annoying. Well done! ?
It's nice to see how you could do this. I don't think I would build an chatbox for the reasons as Georgiana told us. It felt as all lot of work for something that can be done with webhooks instead. As an example; last failed release/pipeline. I would expect to get this information right when it's happened and not when someone thinks, what's the status of the latest release? But that's me. ?
Wow! I was going to this talk with the idea; how can Michael fill an presentation of 45 minutes with this subject. He did this very well with introduction the difference of feature toggles, taking us with the always hard question of; building your own or buying an saas solution. I liked this part! The talk was finished with great (enough) examples. The conclusion was not an added value for me. ?
For your second talk, in English, being a non-native English speaker; this talk was awesome. You are lovely to talk to off the stage, and you bring this authenticity and excitement to the stage.
One improvement you could make would be to rehearse your talk until you are so comfortable with the timing that you couldn’t rush it if you tried to. Really, the trick is to keep reminding yourself to slow down and to drink water and to breathe. The talk is interesting, so it won’t bore people even if you slow down.
Conferences could use more talks on this topic, and I’d love to see this talk in one of the upstairs rooms next year.
I missed the learning points in depth. For me it was something like; in the past we didn't do X but now we do. And that with an lot of technologies. I was expecting (by Rafael mentions) an more in depth inside of the reactor process. What's went wrong? How did problem got solved? Rafael mentions more details of the Prometheus screenshots than Luis did, while I had expected the other way around. The event steam code example/demo gave a nice effect during the presentation.
Cobucci's talk showed a lot of learnings on how hard it can be to deal with legacy software, with some nice analogies, code examples and a funny interactive demo. It's nice to see all thought involved in trying to drain the big ball of mud and not being ashamed of exposing the mistakes that happened on the way. Looking forward to the next episode! =D
Thank you!