Talk comments

Brad Bird at 17:07 on 17 Feb 2017

Nice talk :). We already use Heroku at work but am really considering trying out Docker now. I've heard of Docker but never knew how quick it was. We currently use Vagrant which is a bit slow so looking forward to seeing the speed differences.

A great insight into how someone else has achieved dockerising production applications with AWS. Certainly a few thing to go back and revisit with our approach.

A very well paced and light hearted talk. Having worked on a monsterous PHP/Nodejs hybrid application previously, it was a great insight into how that could be simplified to pure PHP with websockets.

Could feel a lot of energy from the speaker, but content-wise this talk doesn't seem to be suited well for a PHP conference, as most of us aren't beginners anymore.

Mark Kathmann at 16:05 on 17 Feb 2017

Great talk, although the content wasn't new to me Alena makes it crisp and clear for anyone on the OOP learning path, and she has a very open and personal presenting style.

Gary Fuller at 15:58 on 17 Feb 2017

This is the talk to go to if you're learning about OOP for the first time (or didn't take it all in, like me). I wish I'd had the terms explained in this exact way the first time I came across them. Brilliant!

Great talk, I have thought about the package for some time now, but this talk convinced me. And also as a side application just for the backup of a application not written in Laravel:-)

Great talk, I'll take home screen-icon, push notifications and offline improvements with me back to Norway :-)

Katy Ereira at 15:49 on 17 Feb 2017

Very well presented talk with a lot of useful information; I'd vaguely come across JWT before but had never really looked into it. Now I will definitely think of it for token based auth.

Katy Ereira at 15:48 on 17 Feb 2017

Nice concept, but fell a bit flat. It was either too wordy, or not wordy enough. For example, quoting wikipedia to explain scope... not great. Using cat gifs to try and explain scope instead? Not much better either TBH. Some funny/humorous points, and the general overarching moral of helping people to understand things that experienced programmers would consider basic, but are simultaneously highly confusing to a newbie.

For some advice, I'd like to see fewer GIFs - quality rather than quantity; a few is fine for punchlines, but the amount presented here was a bit overwhelming. Was I supposed to be laughing the whole way through? That conflicted with the fact that the GIFs were interspersed with some very wordy, serious-sounding slides so the presentation ran at two extremes. Maybe reduce the wordiness and the GIFs to try and find a nice middle ground, because the topic definitely had potential.