Talk comments

Ben thoroughly explained why logging is essential and covered some basic logging implementations, before jumping into Monolog and various tools that can be used to collate and report from various logs.
Although this was great at a high level, I think it would have been good to cover some specific examples (or patterns and best practices)
of when and where to put logging calls in code.
It would also have been good to show examples in tools other than Monolog, perhaps as a comparison.

I really like Li3 and I know that Richard is absolutely fanatical about it. If I could suggest anything it would be to jump straight into the code and let it speak for itself (it's really really good code), some developers will get it, some wont. And perhaps spend time, showing where Li3 is different from Symfony, Zend etc, not where it can do the same things. Perhaps show its Mongo capabilities and its ability to behave as a micro framework and how it can scale to full stack.

Code Reviews ironically appear to be more about people than code, and Sebastien hinted at this by suggesting that reviewers should not use the word 'You', but instead use 'It'.
Sebastien covered alot of tech tools - which I didn't find useful, as I already use them.
If I could add an suggestions, then I would appreciate hearing about difficult situations that occur in Code Reviews such as disgruntled developers and how Sebastien dealt with them whilst maintaining professionalism, good relationships and encouraging the developers he is reviewing.

Rob and Evan are both helpful and thoroughly knowledgeable and somehow they managed to cover the ZF2 fundementals into a day, especially emphasising Modules and they're significant role in ZF2.
If I were to suggest anything in the way of improvements, I would propose spending more time on the ServiceManager and EventManager/Events and I felt that this is a fundemental change in the way ZF2 works and a thorough understanding is vital in appreciating and using the framework.

Having seen a variation of this talk back in 2010 I felt there could have been a little bit more information about how people and businesses could get involved other than "sponsor a conference" or "buy beer/pizza". There were a lot of points made though that will help me to provide reasons for sponsoring events to the decision makers at my own company (especially if I give them the slide deck).

That being said, it was a good keynote to end the weekend on and will hopefully inspire other business representatives to start sponsoring events.

The subject was well presented with nice slides. The few scenarios were a bit tricky to follow and I think this could be done in a better way. I would also have liked to see, with perhaps just a screenshot, on how you would do code reviews with github and glassfish.

Good overview of phpDocumentor and it was good to hear some of the new ideas around what is coming up now it has been resurrected. A couple people I know attended that had never really bothered documenting before and now they have a renewed feeling about why I insist on it, so thanks :)

PHPStorm looked pretty interesting but as mentioned the colour scheme could have done with a slight tweak (could have been the projector setup though).

Good content, great slides. I'm not giving it 5 stars as parts of it were rushed because of time constraints. I will need to read up on a few more things again now.

I thought this was a good introduction into NoSQL and some of the alternative situations were NoSQL can be used.

The aspects around ACID, CAP and ABC were well introduced and helped to put the rest of the presentation into some kind of perspective.

Great start to a Sunday morning. I wish it was presented as a keynote as it would have gotten the attention it deserved. Even as a non-UI person, I picked up a few things and I now know it's not as simple as it seems to have a "responsive" design. Instead of Cameron, I'd have picked Boris though as he has a bigger clown factor :-)