|
That's called "rediscovery."
|
|
|
|
|
Maybe. Are you using pointers?
|
|
|
|
|
|
Significant other will never forget that I forgot it.
|
|
|
|
|
That's like "Fail safe systems fail by failing to fail fail safe"
|
|
|
|
|
As opposed to code with proper error-handling which will fail successfully. 
|
|
|
|
|
"Salt is added to a rebate mix up for this mobile temple."
(10)
modified 1-Aug-17 4:11am.
|
|
|
|
|
Tabernacle.
Salt (NaCl) is added to an anagram (mix up) of rebate.
Andy B
|
|
|
|
|
Well that was quick! Congrats.
|
|
|
|
|
My "Introduction to Event Sourcing" talk is getting another run out next month and I am considering doing a show-and-tell of how the CQRS designer works and generates code.
What think you - does seeing some code add to or distract from the talk content?
Consensus seems to be no code - which chimes with my instinct.
modified 1-Aug-17 13:31pm.
|
|
|
|
|
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.
"It is easy to decipher extraterrestrial signals after deciphering Javascript and VB6 themselves.", ISanti[ ^]
|
|
|
|
|
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!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
