Talk comments

Martin Bean at 11:33 on 2 Oct 2016

Very short and unprepared. Also would have expected a mention of Laravel—one of the tightest-coupled framework—in the talk and maybe best practices or tips on how to write code decoupled from that framework.

Richard Bagshaw at 11:31 on 2 Oct 2016

Talk started at 11:10 and we were at questions by 11:25. Also slides were unclear and text way too small. The only advice given was "use interfaces"

Interesting and well presented talk

Calum Bulmer at 11:30 on 2 Oct 2016

I found this talk really useful and informative. It was well delivered and gave a good overview of how essential coding securely is as well as covering other attack vectors to the stack in general and ways to help avoid them.

The information on the Timing attack really interesting and it has opened my eyes to a whole other set of potential attack vectors and vulnerabilities.

Ashley Pinner at 11:29 on 2 Oct 2016

Security is a very large topic and James tried to cover quite a bit of it. A talk bustling with information, sadly constrained by a 50 minute time slot. Despite this, it contains useful advice, even if you think you know everything about security.

Scott Dutton at 11:28 on 2 Oct 2016

Great talk one of the best of the weekend I think. Very thought provoking

Mark Railton at 11:14 on 2 Oct 2016

Good talk with a great introduction to Slim and how easy it is to get started using it.

Tom de Bruin at 11:14 on 2 Oct 2016

Really enjoyed the talk - great overview and potential pain points covered. It would have been nice to see a working example, either live demo (!) or prerecorded to show it all working

Gareth Ellis at 11:11 on 2 Oct 2016

I liked the broad overview approach with examples of how queues could be implemented. Lorna also foresaw my main concern with the section dealing with long-running consumers/workers, which was cool!

Aaron Wardle at 11:11 on 2 Oct 2016

Great talk this morning, we will certainly be interesting some of these ideas in our business