Well, there is some ambiguity here.<p>I would say that I much prefer live coding to code on slides because I can see it actually compile and run. Proof that what is said works, works. I might even get to see common gotchas. It&#x27;s obviously a gigantic failure if we only see errors and never working code, but then that speaks to the nature of what is being demonstrated.<p>With presentations, you can show a chunk of code with a presenter confidently stating &quot;This works!&quot;. Of course, that&#x27;s no guarantee that it does, and frankly if you tried to implement what was demonstrated and it ends up not working, you would get blamed for it. &quot;You clearly did it wrong, you were supposed to do it like this: &quot;.<p>Live coding shows you all the context, because you must show all the context, and it gives you a concrete example that you can yourself run. A working hello world. It does something critically important, it takes the blame of something not working for you, off of you.<p>of course the ambiguity I mentioned are the golang slides, which are actually demonstrable pieces of code. With a little &quot;run this for yourself&quot; button on each slide. That&#x27;s a really awesome solution.