PHPBenelux Conference 2018
26 - 27 Jan 2018 at Ter Elst

Doing this in our own projects, the shared experiences were very relatable, and the examples right on point! Sound advice, clear explanations.

Switching screens and demos not working might be the easy part to fix, so keep at it. Interesting stuff. Still missing that one holy grail docker solution example ;), but damn near close!

Very nice talk that explained the topic very well. I would love to see more of this speaker, keep them talks coming - good job!

Lesson learned: twitter contains spoilers for talks like this. Interesting talk nevertheless!

Quick overview to get you up to speed, but some simple code examples would have benefited the talk.

A talk that might be of interest for a lot of developers. There are a lot of good (and often repeated) arguments in there, but the description didn't fit the content - it's not about your brain, but about probably well-known concepts to keep yourself healthy and energetic. I had expected something entirely different based on the description, and didn't really find the red tape as described by sentences like "our brains are plagued by a raft of bugs and unwanted features that we have been unable to remove".

Worth the visit, but maybe update the description?

Very interesting workshop. Not too fast, not too slow. Might be interesting to setup a repository with the code base, so typing everything doesn't distract that much from what you are explaining.

Really excellent talk. Good content. Good slides. Excellent delivery. Nice take aways that people can start using right away.

However it was too short. Approx half of the allotted time. Another 15mins of material and this would be a 5 star talk.

I have been thinking of doing a talk on exactly this subject and was in 'deja vu' during the whole talk: James nailed all of the topics just right.

I do have some suggestions:

1) Testing was used too broadly: as a replacement for 'automated testing' or 'writing tests' forgetting that developers do manual testing
2) I liked the suggestion of not using Behat to catch stuff by div-id but I would actually suggest people to first start using it just like that: people not familiar with automated testing might find behat/gherkin/selenium very very frightening, trying to get them to write `business like` scenarios could be too much for the 1st step
3) Better interaction with the audience: not that the interaction was bad, it was good but I would really love to see this talk in a keynote format

:+1:

I think it was nice recap