.png){kind=icon}
PHP South Africa - Cape Town
4 - 5 Oct 2013
at Liquorice Digital Head Office
Talk comments
Great talk. Got me motivated to clean up things on a dated project.
Great talk, filled with useful insights. Needs to be on YouTube.
Good tips for developers, though again felt more targeted at PM's. I think it might have benefitted from a closer look at the kinds of applications developers can use to assist in the fight against failing projects.
Very interesting look at what can be done with MongoDB, but possibly not enough about how it looks/works in PHP.
Had mixed feelings leading into it; but they were gone after slide 1. Well presented, and compelling data!
I think some of the MongoDB-specific aspects of this talk were too advanced for the forum. Still, you did a great job in the take-away which was to be prepared.
Great topic but I think Paul's talk beat you to some of the magic here. I would definitely like to hear more from you though. :)
Great talk. 30 minutes was not enough time though. Needs to be the subject of a workshop and/or a series of tutorial/blog posts. I would print those posts out and stick them on the faces of some developers I know.
There were some good ideas in this talk, but I did get the sense that some of the approaches were not met with supportive responses during Q&A.
This touched on many of the practical uses for annotations (e.g. dependency injection, data modeling), but the presentation seemed to tread lightly and stop short of really making a case for them -- this may have been your delivery and not the content itself. Contrast this with Rafael Dohms' presentation on annotations (several recordings are out there), which makes a strong argument for them.
While there were a lot of code examples of annotations in use, I think devoting some slides to how the various parser implementations work is called for. Based on the slides, I saw a bit of the Reflection API, but not enough to create my own annotations. Perhaps the slides were focused on Laravel's implementation, but the annotation examples also didn't cover some of the complex values/parameters that Doctrine's parser allows for (e.g. named parameters, nested annotations for things like an array of database indexes).
Mentioning PHPUnit as a long-time user of annotations (I believe they use their own parser) would be great as well, since many developers use things like @expectedException and @dataProvider without a second thought, although they might be hesitant to use annotations in their own application code.