The first step of working with legacy code is realizing the incredible amount of value that has dropped in your lap. In this talk, he is going to pinpoint that value. And move that value in a better to maintain and understand codebase.


Comments are closed.

Tim Haselaars at 13:31 on 20 Sep 2018

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!

Gabriel Somoza at 13:31 on 1 Oct 2018

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!