PHPNW 2014
3 - 5 Oct 2014 at Manchester Conference Centre

The subject matter was interesting, the tutorial plan reasonable and Michael a really nice guy. However he had trouble keeping everyone on the same page. I expect this is in part due to it being the first running of this tutorial but also due to the system config dependent nature of the software.
Perhaps insist on a specific installation version of Vagrant, Ansible and Virtualbox?

Good talk and the pace was about right for me (though that's perhaps because I already knew about some of the bits). Appreciate some people may have been using the 5.3/4 stuff for a while and only wanted the newer bits, but for those of us stuck on 5.3 (and who only get to go to conferences every few years) it was good to see.

Will hopefully provide some ammunition for those pushing to upgrade our versions at work too :)

Good talk about Codeception and what it can do, though I do agree with the comment above slightly: sometimes it did feel more like a (very good) 'Saturday' talk explaining and justifying Codeception. At one point I did wonder if it was too good to be true having not managed to get a test running at that stage; once I had it running in the second half of the session and could play about with it things made more sense.

Still a great tutorial, would be even better if it was mixed in with the talk a bit more in the first half. The instructions in the readme could have a been a little clearer in places too, but that didn't matter so much as Jeremy was very helpful.

As mentioned above, the ready-made VM helped a lot; would have been even better if I could have got hold of it a few days before to get it all ready, but that's probably just me (I'm fairly new to Vagrant, not that it's difficult).

Worth hearing as a reminder that just because we don't do waterfall any more (yeah right!) there are still parts of that process that can, and should, be adapted to whatever process you adopt to replace it. Agile involves breaking the work down into smaller more manageable chunks, and so why not do that with the design too?

I agree with what everyone's said about the reading bullet points from the slides thing, Davey's trick of having the bullet points in there but not reading from them & skipping them largely, but they're still there for when people view the slides online later is a trick I'm going to pick up myself & would have really helped this talk too.

Content wise I thought it was spot on, code reviews are not a gateway to production or a barrier that has to be negotiated, they're an opportunity to learn, for the reviewer as well as the reviewee so thinking hard about how you provide feedback is a must.

Good talk - the project deserves more exposure from what I heard in this talk

This was my favourite talk, perfect amount of humour for the end of conference. Many laughs throughout but more importantly many many serious points which resonated with me. Was left with a lot of food for thought.

Fantastic and mind blowing talk.

Really refreshing too, to see someone with the depth of knowledge and expertise of Anthony, go (somehwat?) against the stream and present a totally different approach on OOP for solving software problems.

Thinking about the flow of information through an application and about how the different objects communicate with each other makes so much more sense than following whatever "design rules" book to the letter. At least to me it does.
Ask, tell, translate; sounds simple but the way Anthony explained it, it could also just work.

What I also took away from this talk: being a good developer is not about using design patterns all over the place.
For the life of me I've never been able to keep some of those patterns apart, the details that -supposedly- made them different were just beyond me. Or so I thought.

To all of you looking for the book or more about it: Anthony did mention the blog posts that led him to this talk: http://blog.ircmaxell.com/search/label/Beyond

I do agree with the guys asking for more (reading material) on the same subject but I'm hoping it won't be (interpreted as) a new rule book ;-)

Great talk by a passionate speaker that covered a lot of ground.

I think that in the future maybe skip some parts to make it slower and focus on less content. Try to never skip slides, it confuses people and they feel like they are missing out, I'd rather have some extra "Bonus content" that the crowd would not know about after your thank you slide.

Other than that, amazing and thanks :)

Really informative talk and delivered what it said on the tin. I was thinking of playing with GAE and getting to know the experience of someone who has done it really was helpful. Good examples and nice pace.