Talk comments

Tom Cannaerts at 20:15 on 31 Jan 2016

Always nice to see results from actual real-world investigation.

Tom Cannaerts at 20:08 on 31 Jan 2016

Good keynote, but maybe a bit to long for my taste

Harold Claus at 18:22 on 31 Jan 2016

Good talk by great speaker! Started basic and ended mid-range. Demo's were very clear.

Did not attend the talk itself, but judging from the slides alone the whole webdev world needs a big wakeup call :)

Great talk on an important subject! Inspiring!

It's very hard to explain abstract concepts in a way everyone can understand and follow it, but I think this talks does exactly that. Impressive.

The surprise of the conference for me this year!

Loved the concept and approach of the talk and the way you explained this 'thinking' theory, tie it to the world of development and tried to put it into practice with the raffler.
I agree with what you said yesterday that mixing up the theory and the example a bit more could work better, though you might lose the big laugh.

@Ramon; One thing I would really change is the abstract: it reads like you're giving a talk on "learning from your coding mistakes". It doesn't say that of course but since what you are actually talking about is quite different (and as an abstract-reader you simply have no idea), it's easy to assume the above.
It had me fooled and from what I've heard quite a few others too (and actually prevented them from coming).
And that would be a real shame!

Gary Hockin at 17:07 on 31 Jan 2016

This was my second favourite break of the entire conference.

on Break

I know there's a lot of developers out there who think they know all about composer already; well all I can say is: go see this talk!
Good structure, great fun, and very, very informative.
After this talk you'll know how to use composer like a real PRO.

@Rafael:
Please also put in the abstract for the next cfp that you explain the 'composer init' side of things, cause I've never seen (or read) a better explanation of how you would go about and create your own package (for proper use with composer and packagist): what things to consider regarding dependencies and semantic versioning, readmes, changelogs and beta mode.
It would be so nice if everybody got it right. ;)

Thanks for the positive feedback, all. I really had no idea what to expect.

I added my slides, with "slight modifications" to preserve the quality of the talk. [chuckle]