Fantastic talk and the sort of thing that justifies coming to PHPNW. I love hearing about ideas on how to better architect code and I'm a big fan of the idea of writing more to save on reading later, so it was really cool to hear such a practical angle on making code more easy to reason about.
Too much content for the time, and the speaker had to speak much too quickly as a result. The structure also felt a bit muddled and it was hard to pick out the key points amongst all the large code samples and diagrams.
An interesting talk with plenty of practical tips. For my tastes, the content leaned too far towards "here are all the options" rather than"here is what we have tried and these are the advantages & trade-offs".
The speaker spent far too much time with his back to the audience and looking at the screen behind him; this was distracting and made the delivery less engaging. I know I struggled with this in my first uncon talk and it just takes practice and a build up of confidence. The delivery also needs a bit of polish to reduce the number of "ums" and "erms".
This was a very good talk for complete beginners to OOP, delivered with energy and passion. I think the speaker needs to be aware of the British public's aversion to audience participation!
This was probably too basic a talk for such a conference as this, so it would probably be worth flagging in the abstract that this is for true beginners.