Great opening, I absolutely loved it. It was witty, well-prepared (although it seemed very natural), and prepared everyone very well for the rest of the talk. As you continue to develop this talk, make sure to introduce similar elements throughout the rest of the talk to keep it fun throughout – which it still definitely was, but maybe with less impact as the opening 5-10 minutes.
Regarding the rest of the talk: very useful information, insights and tips. From experience, I would consider not mentioning "DDD" at all and just talk about Value Objects directly: just saying "DDD" creates really high expectations about certain topics – and that wasn't the purpose of this talk. For example, Value Objects are a concept of their own that exists also outside the realm of DDD, but they may be coded quite differently in the context of developing in DDD vs refactoring legacy code. So instead, you could just memorize a good generic definition of Value Object and not mention DDD at all. Additionally, I recommend looking for a better example of how Value Objects can help refactor legacy code: the example was good, but I've seen other other examples that lead the audience much more effectively to an "aha!" moment.
But those are very minor details: this talk was great to listen to, and I look forward to hearing how it evolves in the future as you gather more examples and tips!
Very interesting topic and tour of the Oh Dear! app. Would have loved to hear more technical details, e.g. how certain technical challenges were identified and solved / prevented, or a more in-depth review of how the queue systems work, etc. For technical audiences, I think you can condense the part about what the App does or the background information about how it was conceived (but I personally enjoyed that part too).
Credits to Frederick Vanbrabant to keep it funny and relevant at the same time. Learned new things and recognised a lot of experiences.
Small tip, You interacted with the crowd and where moving around, but when you stand in the middle in front of a slide, it makes it hard for the visitors to read what is on the slide
In your talk you explain a lot about the reasons, best practices and approaches, but I missed some personal dirty details on real experiences or some concrete cases or typical recognizable faults (we all make). You can keep them anonymized but it makes it all but more concrete.
Don't let the small feedback stop you, I really liked the talk and I was amused by it while learning how to tackle it.
Keep on doing it!
Very good and interesting product talk with some insights on the code side of it.
I would be interested to hear more about the architecture and how the data flows.
Numbers are always good to mention, like the amount of traffic, how did you worked on the it, ...
From a code & business perspective, you made it look very easy but love to hear what the goal is