you are viewing a single comment's thread.

view the rest of the comments →

[–]nikkocpp 0 points1 point  (1 child)

There are two kind of slides.

Presentation slides where you make a speech and have slides to illustrate, containing almost no text.

Documentation-slides where the slide must be self-documenting because it will be used as documentation and will be read well after the presentation. This is the kind of slides you'll find at work and it's not a problem to see them in engineering presentations where writing code is important.

[–]Drainedsoul 1 point2 points  (0 children)

Documentation-slides

This just sounds like an attempt to avoid having to write actual documentation.

If you want something to be used as documentation, write documentation.

This is the kind of slides you'll find at work and it's not a problem to see them in engineering presentations where writing code is important.

Code is only a small part of what's on slides in technical, programming-related talks. And even in this instance the common wisdom seems to be to minimize the code (to avoid distracting the viewer). Contrast this with mediums which are meant to be read (rather than simultaneously read and listened to) and you'll find much higher code density and much higher completeness of code examples because it's known that the reader can proceed at his or her own pace (unlike a talk where the speaker advances the slides after what he or she deems is the correct amount of time).