rendering et alter...
You didn't say anything about your audience. My feedback is that you have WAY too much information on each slide. You have enough material there for several hours. If you are talking while these are up, your audience is going to have a lot of trouble taking it all in.I strongly recommend you have a dry run on a willing volunteer. I did this with a buddy of mine a couple years ago and his 30 minute presentation took 2.5 hours to get through.I started skimming at about slide 11 when the type got teeny tiny and it took me more than a couple seconds to read a slide. I then had to go back three slides and go slower. Some of the text on the later slides is so small it is completely unreadable on scribd.That said, the content was quite interesting.(On slide 18 it is "Structures of Arrays" not "Structures or Arrays".)
Hiawesome presentation full of useful tips.i spot a typo error on slide 16:Tree *l, *r;Martin
Great presentation, I will link it to all of my c++ coder friends :DBut as Rob said, it will take a lot of time to present it.Ps : design may be a bit austere :)
The content is great. The presentation not. Waaaaay too much text on most of the slides...
It did get me wondering if the Pepsi and M&M adds between the slides say something about me :)
I'll fix the typos, thanks!Yes, the slides are long and have too much text. On the other hand, if I posted "presentation" slides probably they would be of no usefulness without me presenting them. The slides are currently designed for reading :)
love the presentation. i've never seen you mention haskell once though in your language polls or references to what lies out there in the future...seems curious to leave it out
brad: I added it to the language list if U check it out now
Seems very reasonable, though I agree some more custom graphics would enrich the presentation. F.i. draw some loose chart of code-complexity against generality of code or other abstract attributes (page 6) instead of text statements. People will be more immersed and on top of that can follow your words.
really great content here. i agree with the others though. this needs to be a lot shorter. i just gave a talk with a whole lot less content than this (20 comparatively sparse slides) and its first run still went well over an hour. In order to make the talk 20 minutes I had to cut the slides down to 10. you can always leave the details at the end for reference and those that will actually read the whole thing on their own (like me)give it another pass through and prefer graphics over words. your words during the talk will be enough.that being said - i am downloading these slides before you chop them into user-friendliness. good job! :)
What I found tremendously useful about Mike Acton's presentation was that he explored a small issue with great depth. This presentation is more like running past the library. Unless you're presenting this to students or folks outside the games industry I think you need to focus on a small subset of the material.Personally, I would find it useful to read a presentation that took a slow, overly general system and rebuilt it as a low-dependency high performance system.p4. Adeguate -> Adequate
is the presentation in its final form by now?
just wondering whether it would evolve or not :)it was quite interesting but (maybe i dreamed this) i thought it was marked as "draft" when i first opened it
and actually it still says "presentation draft" :)
Ye I dunno if I'll change it more, it might be. Surely I'll cut it when I'll actually present it but for the "web" I think the full length version is better.
Thank you for the answer and of course for the presentation!
Post a Comment