I agree with rooster ^^. Moreover, I expected a specific Zend Framework contributing talk. Nevertheless some good pointers and I like Matthew's presentation style as it is to the point and easy to listen to.
Very easy to listen to, but I missed some stuff like how to effectively use svn:externals for common code base management, and maybe some more in-depth of the actual *management* of the releases. But, that's more of an expectation issue, the content of the presentation was fine.
Liked it very much. Lots of very useful tools and tips, and easy to listen to.
I had expected a bit more light on the "process" of quality assurance, and a bit less on the "automation" of quality assurance. But what the hey, you're not there for my expectations ;)
Very helpful and practical session! I am amazed with Derick's patience with his audience. XDebug is a great tool and I am very anxious to get it running in my day-to-day IDE.
Derick, next time, ask for thumbs up and thumbs down, in stead of "is this working for everyone?", might work better :)
This wasn't really about PHPSpec but why and how TDD should work for you. I would've liked more hands-on info about the tool, because that's what I expected. Why would I want to start using PHPSpec over PHPUnit?
Some really valid points about design though, but they would fly for PHPUnit or Behat as well. I would suggest extracting two talks from this mixed message. Either talk about design and TDD, or about the tool. :)
I should have read the excerpt a bit better before joining in with this talk. As someone already being a team lead I was hoping for some insights I had not run into myself, which it didn't contain. But that's purely from my perspective, I can totally see this talk being helpful for someone the talk is targeted at.
This might have been the talk that stuck with me the most. Very interesting topic and I enjoyed the fresh way it was brought. Structurally, content-wise and presentation-wise an excellent talk and I am definitely going to dive into the topic more. Fun fact: had a campfire conversation with my two brothers explaining the question about the rectangles and lateral thinking and De Bono, etc. Awesome campfire conversation material, if you ask me :)
Interesting topic, not the best talk though. I think it needs some work on the structure and the content. For example: it was confusing that at one point we were talking about LinkedIn and a minute later about Github, as an example. It might be better to pick one example and stick by it.
Got me looking into graph databases though, so thanks for that! :)
I really enjoyed the fact that you didn't bother to relate to PHP. And what's not to like about a game? I think it would be worth it to put in a slide that points out a few notable things about the game, such as the fact that it is 2d, turn based etc. I would personally not have focused on the menu because that really took out the fun of the fact that you were telling about a game (damn, back to websites again.....). I'd suggest to dive into the way a turn works in this specific game and then explain how it was implemented using event sourcing, so for example rolling dice, adding/subtracting points based on that, etc...
This started off real promising but at some point unfortunately changed into a feature listing of the Symfony DependencyInjection component, even though it started with a "this is not your 'yet another DIC framework'" reassurance. Nearly everything in the presentation was implementation detail and really no longer had anything to do with what the talk's topic promised to be in the first 10 minutes. Too bad because the slide about how Events, AOP and DI relate to each other really made me enthusiastic for the topic :)
I think the concept of mutation testing itself should get more attention. My colleague sitting next to me (a bright guy I can tell you) did not even understand what it was. Next time I'd suggest to try to do the talk without the tooling, and explain how one might implement such a tool, starting from the beginning, and trying an example
Oh and please don't sum up a list of command line options and installation methods. That feels like the worst kind of pastime in the department of time wasted :)