PHP UK Conference 2018
14 - 16 Feb 2018 at The Brewery, London

I didn't know how Gary could top their keynote from last year.... and yet it happened! Really great message well delivered.

Lots of good advice; new developers should heed all of it and everyone else most of it. Good analogies and screenshots, well linked to the "gaming" topic. Minor thing (I mean really) but you moved side to side a lot on stage and from further back that made it kind of hard to watch you!

Thought provoking talk with some interesting tips to chew on

A well-balanced and interesting talk. Webhooks seem simple and obvious but they have hidden depth which Lorna walked us through clearly and easily

Excellent - and I love the rabbit pauses ;-)

Thorough talk with many strategies for optimising doctrine entities.

Also provided a good introduction to doctrine

Already knew some of the content but the configuration of Jenkins in code was new to me. A brave choice to do a live demo but it went pretty much flawlessly so can't really give less than 5 thumbs up! The new Jenkins UI looks great - might have been nice to see the whole presentation using it, but understand that adds extra practice requirements.

Solid talk recapping the last 14 years of PHP communities with a great level of research. Opinionated, as fits the subject matter, would have been interesting to go deeper into how companies profiting from user groups have more of a responsibility, and how often the burden ends up on the few rather than the many, though this was hinted at. Encouraging to see the depth of support for user groups within the PHP community laid out on screen in numbers and quotes.

Told us everything we need to provision and deploy infrastructure, as well as some more advanced Terraform concepts. Slightly more on Ansible would have been nice but that wasn't the focus so fair not to include too much on it - likely worth its own talk!

Well presented structure and a good set of tools to achieve the aim of migrations with no down time. I was able to ask a question at the end about how this would be managed with feature branches rather than trunk development, would be interesting to cover whether it's possible for those using feature branches, what would need to change to achieve it.