Great talk, well aligned with topics i preach myself, really valuable to any developer who open sources code or works with a team.
I think the response to previos feedback affected a nice rounded talk, i would remove the tooling and really stick to the principle of the talk being able to make you identify these issues without need of tools. Also i would work SOLID into the talk with more of a "this is equivalent to the S in SOLID" way, so that it gives context.
Great job.
Very good interesting talk and I took a lot from it. As a long time developer, some of the practices seemed inefficient and verbose, but I have to accept that the days of obsessive micro-optimisation are gone. Welcome to the days of obsessive code cleanliness! CPU cycles are much cheaper now than developer cycles, so code maintainability is rightfully today's belle of the ball.
Sorry but I didn't find this a strong finish to an otherwise excellent conference. I found that Michelangelo was too quiet and monotonous in his delivery which made it very hard to follow, and the content seemed padded out in need of some serious zest.
Really loved this talk - so much meat on the bones! Some may say too much technical content, but that's how I like it - talks like this can be springboards, laying the groundwork which you can then research and experiment a bit more with and thus end up getting your head round some pretty big new concepts.
There's always an issue of time with these short conference talks - should the speaker keep from going into much detail so that the content remains manageable and the audience can keep up at all times? Alternatively the speaker will choose to give a little bit more than can easily be digested at the time, so the audience go away with new ideas still swirling around their heads not yet fully understood.
Both can work, and I think Ian was a great example of the second type of speaker. Thank you!
Really good and informative workshop, Thanks Derick.
Just a note:
Might be useful in the future to distribute a link to the slides at the start of the tutorial, will make it easier to catch up if anyone falls behind.
Sebastian did a good job of covering a big subject in a short time. Good introduction, good characterisations of what not to do, and of course some good examples of best practice. There's obviously a lot to it though, and some book recommendations or website suggestions for further reading would've been appreciated.
A good 'tag team' talk that was engaging and inspirational. As previously mentioned by other commenters, the content is not going to be new to many of the audience, but it served its purpose as a pep talk to inspire me to become more involved in the community.
Good talk overall, what I'd have liked to see would be some real-world metrics comparing performance of some of the datastructures discussed with an implementation based on arrays. I think this could have given a clearer idea of when it would be worth using a more tailored data structure. It was unfortunate that the slides were hard to read, but not much the speaker could do about it - I don't think the bright spotlights shining on the screen helped!
This was a great overview of the DateTime class that I found very useful as a user of the old school stuff. When you're very familiar with how older techniques work - and when they don't - it can be hard to find the motivation to switch to a new paradigm. Derick's talk covered all the necessary bases to make that transition painless. I've always known working with time is messy - just didn't know how messy thanks to the politics that tags along with timezones!
Interesting talk Derick, thank you! Good technical level, sprinkled with factoids that can be brought out at dinner parties.
This is an under-rated topic, developer really need to start picking up on documentation more and more and care further for those details. I really liked the overall idea of showing things on a concrete example and then showing the results.
Delivery however lacked a few things. Preparation is very important, issues like font size, theme colors should really be tested before hand or at least you should know how to quickly fix them. (the projector did not help also). I think a little more structure would be better to keep everyone on schedule, it could all be done on slides, at least as a backup.
Overall a great topic and important one to be approached.