Getting yourself out of trouble with PHP anti-patterns

Really enjoyed this talk, lots of practical advice and good resources mentioned as well.

Restored my faith in the power of swearing. A very informative talk with some great real world examples to illustrate the points.
I'm off to buy a copy of the anti-patterns book.

Personal favourite talk of the conference day 1.
Neal's talk often got "too close to reality" for comfort as he explored the common headaches that developers face day to day, and how to approach them

Well presented and lots of idea and helpful examples

A lot of real practical examples, painfully real. Brilliant presenter as well.

Great speaker, engaging talk. You won’t get a chance to lose focus! The topics were clearly illustrated.

Finally some one who almost swears as much as me.

Good and meaningful material

An incredibly useful talk, with lots that I can take away and apply straight to what I'm working on now. Thanks very much

Thanks for a really enjoyable talk, with plenty of frank analysis and useful insights.

Very real issues dealt with.

Good stuff. Entertaining as always. Lots of great practical content for everyone.

Saw Neal speaking the first time and the talk was really amazing. I just had sometimes problems to understand everything because he speaks soooooo fast :-)

💥. Neal is an enthusiastic, knowledgeable and charismatic speaker, who knocked this out of the park. My 'talk of the conference'.

Probably my favourite talk of the conference. Lots of good examples, and I loved the way it was presented. I think this guy could do video courses easily, as he was very easy and fun to listen.

Really interesting talk amazing real-world examples!

Really enjoyed this one too. Loved the presentation style and I'm sure it's stuff that all developers have experienced, can relate to and learn from.

A good talk with lots of good examples. I like that you talked about how you analysed the code to find the answer for things rather than just presented the problem and solution. Such as pointing out how you would dive into the commits to see why something was added.

Just seeing the "if return true, else return true" was sadly on the nose because I've literally seen it within the last year.

Maybe went a bit too fast at points when presenting but understandably there was a lot to cover.