I like this talk. It explains a lot about the process of static analysis by actually doing it together with the audience, which made this a very interactive session. I'm sure most audiences would enjoy this approach and Damien has enough humor and energy to pull it off.
The talk will probably be talked about and remembered most because the Damien went way over time and kept on going despite warnings, which is a shame because it deserves to be talked about on it's merits.
Great talk in many aspects. Your humor made it really easy to focus for the full 45 minutes (and a bit). The interactivity with the audience was awesome. Clear explanations of why certain practices in code could be considered good or bad (and no, I did not miss the disclaimer that this could not be inferred from usage count only).
Easily the best talk I saw at the conference. This talk has great material to reflect on, relating to (probably inspired by) Domain Driven Design. But even if you don't know or maybe don't support those ideas, you can still get some good value by watching this talk. And the bits of Bruce Lee history doesn't hurt either :-)
I did feel a little stupid because of the visible disappointment of the speaker when nobody recognised the pictures of Grace Hopper, Dennis Ritchie OR Edgar Dijkstra. I did recognise Columbo, but somehow that didn't make me feel any better.
Great talk, saw some good stuff I'd never heard of. Easy to follow, pleasant to listen to.
Gary rocked it. This talk is good anywhere, anytime for any crowd because there is _no way_ anyone knew all those tips already.
I enjoyed this talk, it's very open and honest and funny (including an apology for "everything" because the speaker is American :D). I've only recently begun thinking of myself as an introvert, especially the draining effect of being around a lot of people is recognisable. As I am also an employer, it was nice to see and feel a little bit how things look from an employee's side of things.
As a tip, I think the slides could have been a little more polished, or maybe contain a little less list-style content. The talk is strong enough without them.
Great talk! It really got me thinking about the subject and made me realise I need to research more about it and be more aware of it in daily work life. The only thing I can comment is that most of the talk was very much based off of American work culture and work ethics, and it didn't always quite resonate with me personally. Maybe you can tune the content a little bit more to the audience, depending on where you give it. Other than that tiny comment, great work!
The talk started off bad. 10 minute commercial about their company, that's definitely not what I attend for. I didn't really get much out of it, personally, because we already implement 80% of the tools and techniques mentioned. Obivously can't blame that on the talk. However, it was more on a level of namedropping some tools and services instead of explaining _how_ it was achieved.
Speaker had a very monotonous speaking voice. The person who did the QA was much better at speaking IMO.
My tips: deepen your subject to how you've achieved it, including perhaps some samples, screenshots, code, etcetera. Really drop the commercial stuff, and lastly try to add a little bit more life and emotion to your speaking. Keep practicing and you'll get there :)
Always impressed with Michiel's expertise when it comes to the process of software development. I also appreciated the "I used to think that as well" honesty, it gives more power to the message: Deploying on fridays is not just something you say, but an evolution by the systematic removal of all barriers (in small steps).
The presentation is well structured, well paced and brought with humor.
Speaking style could be a little more polished but that might automagically come with experience, wouldn't really worry about that. Contents of the talk were pretty good, given the 45 minutes time limit. After the talk we had some pointers as to where to go from there, but no real concrete examples of why we should try it, or what it's specifically suited for. I would've loved to just see a more in depth walkthrough of a little more extensive piece of code in which all the concepts like the loosely tied interfaces could be explained with a quick side note.