The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
Now is it bad enough that you let somebody else kick your butts without you trying to do it to each other? Now if we're all talking about the same man, and I think we are... it appears he's got a rather growing collection of our bikes.
That's not a joke - that happens at least once a week at the grocery store: I know that I took the trip down there to buy something, but what?
So I buy some other stuff which wasn't what I came for, then go home and try to remember what I was busy with, making me take the first trip. If I'm lucky, that makes me remember what I was going to buy, and I can make a second trip to the store - this time with a slip of paper where I have written it down.
It should not be too long. Scrolling up and down wildly or rapid jumping between source files will quickly confuse everyone.
Back in the days when we still used transparent plastic foils we always said that with 20 foils per second the presentation becomes a video. Avoid at all cost.
And then there also is the danger that you could fumble because you are doing two things at once: Coding and talking to the audience. If possible, it would be better to prepare the code beforehand and showing a 'paragraph'or single lines after another. This way you can concentrate what you are saying and don't have to worry about writing something suboptimal (or the other way around).
As long as it is rehearsed, I like it. If the person is struggling with syntax, or forgets a method name or just gets build errors, I instantly think of the session as waste of time. Post that, it is me thinking of random stuff rest of the time.
I prefer real examples and implementations during a session as that memory sticks for long compared to someone yapping and showing slides.
I once saw a presentation where the guy had all the code already prepared and assigned to shortcut keys, this allowed him to generate the code on screen with no typing, alright 2-3 keys per method or block.
While the code was appearing on screen he could continue presenting and the audience could read the code without interference. One of the best presentations I've seen.
There is nothing more disturbing or boring than watching someone else type out code, most of us get something wrong and needs to rework the typing and your presentation has just gone down the gurgler.
Never underestimate the power of human stupidity
Well, when i was on DWX at Nürnberg i really liked the live coding talks but on the other hand it's hard to follow up and remember at lot of that stuff. Bonus on that, they recorded the sessions so you can watch it again. That was necessary and good.
I'd say, go for it but make sure the audience can review what you did.