Talk comments

Nice touch with the live demonstration, good talk. Plus, the power stayed on for the entire talk!

good talk, lots of examples - really makes you think

Lots of information about the history and design philosophy of FRAPI, plus what was probably the most successfully executed live-coding demo I've ever seen. David seemed very relaxed too, which helped. Seems like a great tool, thanks for releasing it to the community.

While I might have a little bias because I really like the blogpost this talk was based on, I did enjoy this talk. The slides covered the topic well, and I enjoyed some of the humorous pictures depicting the different types of users. I also liked the discussion at the end and getting the audience to chime in. Now on for some advice:

While listening to the talk, it did sound like the speaker was a bit nervous perhaps. It seemed there was some short pauses between slides as the speaker would think about what in the flow of the presentation was next. Other parts the speaker would pause as he was trying to figure out how he wanted to explain something. Not huge issues, but it causes the presentation not to feel as smooth and prepared.

The best way to solve these problems is just plain old practice. I like to just run through my slides a few times by myself after my slides are mostly done. Helps train my brain on the words, phrases, and concepts I want to cover. Then, I like to give it to a small group to get some feed back. Over time, your individual presentations get better, and your overall ability to present just naturally smooths out. The important thing is to realize about the flow, and just work on making it better.

I enjoyed this talk, I'm glad I stuck around for it. It was interesting to see the logic thought process of redefining the concept of "What is a Page?" I also appreciated the healthy amount of code we saw, as well as the live demos.

I would recommend having a bit more polished & styled demo so it doesn't distract from looking at the demo. Sometimes I caught myself trying to figure out what the shown page was trying to represent. Doesn't have to be anything fancy, but just some CSS styling so it doesn't look so bare.

All around, great talk.

I cannot add much more than what the others have added. I always love seeing code examples, but sometimes you don't have time to cram all that content into 50 minutes. I know I would love reading a more in-depth book on the topic.

Great talk. I really liked how he stepped through the thought process, which I think is the hardest thing for developers to understand. But when they do, it is like a light bulb just turning on and it all makes sense. I also appreciated how the speaker acknowledged the fact that different methods have pros and cons, and in their own way, sometimes the less elegant code had it's place.

Now if my code was always beautiful.

I pretty much agree with the other comments. I felt the presentation didn't have a whole lot of direction or focus. It felt more like a soapbox talk of opinions, which is alright but not what I was expecting. While I've done quite a bit of hacking with Node.js, and understood a lot of the material before hand, I think it left a lot of people in the dark who had no idea about Node.js before.

The microphone and audio didn't help the situation, though that was of no fault of the Speaker.

I believe this presentation was pretty informative. Though is basically was a demo, it covered the biggest mis-understood concept in git (especially those coming from an SVN background): rebasing. It didn't get into much of anything else, but it helped me understand what rebase actually would do, since I was mixing up in my head some of the terminology.

Great presentation. It did all of the major things I believe a technology talk should do. It explained what ZeroMQ is, how it differentiates from other technologies, and patterns and practices for using it in real-life situations. Best of all, though, was it got me excited to try it out.

Extra points for handling the power loss very well and the Jurassic Park reference. :)