|
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
RAH
|
|
|
|
|
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.
Rules for the FOSW ![ ^]
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
The last session I did at SDD, was part slides and part live coding session. Foolishly I hadn't checked what part the organisers would put up in the recorded sessions so the slides are present and match the audio; the live coding session though - the camera was focused on me so anyone reviewing later on would have the great joy of watching me type and explain what was going on, but having that added frisson of having to guess exactly what it was that I was typing.
This space for rent
|
|
|
|
|
I find it really shocking that conferences don't do 3 cameras and edit into a picture-in-picture format. (Slides / presenter / audience as appropriate)
|
|
|
|
|
It's a shame they didn't at my last talk. I had a member of the audience dancing - they were controlling a character on screen through their dancing, using a depth camera. It's an entertaining little segment 
This space for rent
|
|
|
|
|
Well at DWX they only recorded the screen of the presenter and the mic audio. So you don't see the actual person but all he showed on screen which in this case is way more usefull
Rules for the FOSW ![ ^]
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
Will you be topless?
I barely recall seeing only one such presentation and it might have been at the VS 2010 launch. It worked ok, but the presenter must have been well rehearsed.
On the downside, the talk centered on some parts of .net that I'm sure were created specifically so that a presenter could do that and get an 'ooohhh' from the audience -- i.e. not features that should be used in production applications.
|
|
|
|
|
PIEBALDconsult wrote: I barely recall seeing only one such presentation and it might have been at the VS 2010 launch. It worked ok, but the presenter must have been well rehearsed.
Standard ms presentation. Kicker is often those wow features are nearly always ms catching up with stuff other's already have - can still remember about 5 minutes into a presentation how excited they were about this all-new windows feature 'multi-tasking.' Even worse some management knobs in the audience actually applauded. (heard that as I walked out and went home even though still on company time.)
Sin tack
the any key okay
|
|
|
|
|
As others have said, keep it short with either pre-written code that only requires minor tweaks or prepared code and shortcut keys.
My beef with doing this is due to taking notes during the presentation. If I am following along, I suddenly can't because I don't have the code. If you provided me the link minutes before the talk starts, I won't have time to grab and install it, I might have localized bugs, etc.
|
|
|
|
|
What others have said.. watching someone type code is both boring and unhelpful. Showing screenfuls of code isn't terribly informative either -- too much, and too much detail, to be able to write notes on. Far better is to have the code pre-written, and slides where you've highlighted and formatted interesting bits of the code that you want the audience to notice.
If you must do some of that, keep it for the Q&A section of the presentation and be sure to practice making the font large enough to be read from the back of the room.
|
|
|
|
|
I despise "live coding" talks.
There's a guy who does C++ videos with live coding. He has great information, but the videos last much, much longer than they should as we watch him write unrelated code and make lots of typos.
The last live coding talk I attended in person was, I think, for the Visual Studio 2010 rollout. The speaker burned up an hour, perhaps two, and covered next to nothing. By the end of his talk, the room was almost vacant (I was on my way out when he finally finished.)
Showing code (not "live coding") can work, but it better have real substance and not be someone mumbling while something very slowly happens.
|
|
|
|
|
|
Hah! Dilbert is wrong, they go in the Bitbucket[^]
I also archive my stuff to WOM (Write Only Memory) on deletion to preserve it for the future. Most PC's are fitted with some WOM, but I paid extra to get infinite capacity WOM fitted to mine when I bought it, just so I wouldn't run out.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
No - I keep them in the freezer compartment[^]
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
You are using my WOMs? They are still looking for me for selling defective RAMs as WOMs, even if they never were able to disprove that the memories stored the data permanently. Good to know that there was at least one satisfied customer.
|
|
|
|
|
They goto east hyperspace[^], as they always have done. How many innocent bits I already have sent there...
|
|
|
|
|
Don't they just go out of existence by putting them together with their quantum counterparts: dark ones and dark zeros?
BREAKING FAKE NEWS: Trump told the truth!
|
|
|
|
|
No, the ones and anti-ones (a.k.a. zeros) already self-annihilate if they ever get too close. That's why we have to keep them apart in separate bits. I always thought the dark ones and zeros are what the black hat hackers use.
|
|
|
|
|
There are no stupid questions, only stupid people. 
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Richard Deeming wrote: only stupid people
And then there are the PHBs. A whole new dimension of stupidity.
Also, on Star Trek Voyager they would probably say that this represents a fundamental shift in the balance of power in the Alpha and Beta Quadrants.
|
|
|
|
|
Just turn around (or restart? I forgot...) the warp core and everything is fine again!
|
|
|
|
|
Shiney new MVC project. Looks great, does what it says on the tin...
Until I deployed it to the webserver and it doesn't look right. Not right at all.
Checking everything... is the css deployed properly? The javascript? The pages? The Assemblies?
Then I started playing around with the web config since it was the only file that appeared to be different from debug to release and, sure enough, if I commented out the compilation entry, everything worked fine. WTF???
Some hours later and getting nowhere, I left it alone and put it back to how it was.
Next day I start again. Had a flash, check the deployed page source, maybe something missing or wrong???
Cut a long story sideways there was a missing curly brace in the bootstrap.min.cs file that was present in bootstrap.cs. How did that happen? I have no idea (of course it was my fault!).
Lesson: not everything that looks like a culprit, is one.
Happy days.
|
|
|
|
|
|
Yup - that's the one! The very last curly brace was gone!
Of course, I only seek answers here, I would never use another web site...
|
|
|
|
|
Yeah man, it's always the simple stuff that gets us. As engineers we love to think, much to our determent. So when a problem arises we tend to think of the more complicated solutions first, and it's always those damned semicolons that get us because we overlook them. 
Jeremy Falcon
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
