Congratulations to the speaker, this was an awesome talk about Docker multi-*.
He put everything: live-coding, graphs, data, and much more in 50min, with no rush and very clear.
I felt that this talk could be a little bit longer, with more examples, as well live coding. It was too much superficial.
I know the library, but if I didn't, I wouldn't see its potential just because of the talk.
I did not like this talk, the speaker is young and engaging but sadly the concept expressed do not share anything with the microservices concept.
I simply attended the presentation of the refactor of a legacy code base using nice solutions derived by mixing GRASP pattern and clean code suggestions.
In the end, might be an interesting talk but the target has to be reviewed.
I loved this talk, Abdala is a brilliant guy and he provided a lot of interesting concepts. I enjoyed his presence on stage, he's engaging and always smiling.
He has been eager to listen to one problem that I faced and the solution that I found out comparing it with his approach.
Really nice :)
I really liked the setup with different code examples and lots of useful theory. You showed examples that others can implement right away which makes it really powerful.
Some code examples were a little bit dark and sometimes a bit harder to read. The code itself is great.
Thanks for this amazing talk!
This is the second time I see this talk, is it still as great? Yup!
What can we learn from this?
The talk defiantly had some potential however there are a couple of areas in which I think it could be improved.
1. The title.
My expectation from this title was something along the lines of a talk detailing the work of splitting a monolith into microservices; consider thinking about a title which better reflects the content of not needing microservices to write clean modular code.
2. The length.
Ran a bit short for the time slot, I think you were expecting more questions but this can be quite hit and miss. There are a number of ways you could go to add new content: consider covering some more theoretical areas behind the choices made or showing how you might evolve the code further in future work.
3. Code samples.
Consider having multiple slides with the same sample on with areas of less interest greyed out and other areas highlighted which you can move between as you talk about the code. Alternatively consider removing less interesting bits all together eg the content of the SQL queries had no huge bearing on the refactoring you were doing.
Great explanation of why memory leaks happen. Clear examples, great slides. A talk that everyone could do with watching.
Fantastic talk. Great content and very entertaining speaker. It's given me lots to think about. Thanks
The speaker clearly had knowledge and property of what was presented, and the talk couldn't be better. Congratulations on the material that was shown.