I expected more practical tips or examples on designing a UI for an application.
For example, the first working version of something I've developed always has the worst GUI, because I want everything to work and then worry about design later, what are good ways to make this crappy GUI better?
Loved it! It's great to see Douglas Crockford in the flesh. I've been using JSLint with great success for about two years now. I also loved the series you did for a Yahoo (History of JavaScript). One point of criticism: You started off with a psychological approach to how programmers program, which is the foundation for explaining some of the not-so-trivial (in JavaScript) code styles, as enforced by JSLint. I understand why you added it - trying to side-step the minefield that is code-style preference - but it felt a bit slow.
Please keep fighting for us for a better JavaScript! :)
I learned from this talk. However I did think it was more an introduction to doctrine2 and a helicopter view of the framework. This view could easily be obtained from reading the documentation.
Some more talk about the framework itself and less about doctrine would have suited this talk better in my humble opinion.
Risky topic: bringing front-end development to developers. With a last-minute laptop switch, things didn't go according to plan (missing fonts..) but Mike took it well.
The talk itself indeed was a little slow and it would have been great if at least one front-end framework would have been treated.
This guy is awesome. Really knows what he's talking about. I wish he'd have more time to go in depth on this subject. Pros and cons. Especially on Varnish Cache. Storing sessions in Memcached in a multi-server environment was an eye-opener to us, we were struggling with such a problem for a client. A lot of tricks to try...
Thanks! Hope to hear more of this guy.
Great kick-off of the day. Enjoyed it!
Yep, a more hands-on approach would have been great, but I must say that I enjoyed it very much. Saw a whole different side of PHP which I didn't use that often and some common pitfalls were discussed, so thanks for pointing those out!
I enjoyed the interaction with the speaker. Teaching PHP in the academic world is apparently frowned upon, whereas there are plenty of job vacancies. To Clinton Imgrams: perhaps you can also post your situation on http://programmers.stackexchange.com/ I'm sure you'll be able to find some sympathizers.
I like the idea for this talk but I would have loved to see some more examples. I don't think analyzing the DPC website is a very realistic example; it's aiming waaaay too high. The kind of websites 'developers' make are sites like your phpDocumentor. Choosing the right fonts and colors only becomes important on the very high end websites. I think the focus should be more on content, structure and interaction.