Ankur Satle

On 15-Dec-2020, the C++ language standard got it’s 6th edition – what we fondly call as C++20.The new standard revises the previous C++17 standard.

Buy the new C++20, available as a pdf in English at CHF 198, at https://www.iso.org/standard/79358.html.

Preview C++20 at https://www.iso.org/obp/ui/#iso:std:79358:en.

The latest draft is available at https://wg21.link/std free of cost.

Previously, on 04-Sep-20, the DIS (Draft International Standard) had ended and it passed unanimously. C++20 had received it final technical approval after which the final round of editorial work was going on which culminated into the publication of the C++20 standard.

Previous C++17 standard is available at https://www.iso.org/standard/68564.html.

The C++ language updates it’s standards every 3 years. It is remarkable that C++20 was rolled out without any delay! Kudos to the ISO C++ Standard Committee and to the entire C++ community.

I recently made a couple of presentations about C++, my favourite language, the one that I have a deep-ish understanding of. Obviously, they were all about code being about programming. You can watch them on YouTube here.

Personally, I feel the following tips are the better ones to stick to:

Use different fonts for code and natural language.
Code must be syntax highlighted. It is not just plain text. Show it the way everyone is used to look at it. Keywords, control statements, types, variables, comments, etc. should have their own distinct colours.
Use a consistent font for the code. There should be a theme that the audience quickly recognises and follows subconsciously to recognise parts of your slides containing code and other natural language points. Personally, I prefer ‘Courier New’ for code. It is okay to lift code from elsewhere but it is your responsibility to make consistent.
Code font must at least be a certain font size or larger. One should not have to look around on the slide to spot the code that you are talking about. Also, this is a good way to find out if you are putting out too much code on a slide.
Use animation to bring out code gradually to make your point. If all the code becomes visible at once, the audience will be distracted with code hunt. This needs a lot of thought and planning to go behind the talk. But you got to do what you got to do. Let the constructs appear one by one enabling you to make the point.
Use shapes like rectangles, circles, underlining to focus attention to the part of code in discussion. Use arrows to show how code could evolve/change/move from one place to another as you build upon your concept or point.
Name your constructs well. Guess what, if good naming aids code understanding in codebases, don’t you think understanding is the whole point of the presentation? Do not use with f, foo, bar, T unless you are presenting something so generic that you cannot give a proper name.
Make your point with realistic examples. Often, concepts are well understood but application in real-life scenarios is a problem. The presentation should show also how concepts can be applied. This helps drive him the point.
When building upon a concept over multiple slides, duplicate slides rather than make new ones. This is the most consistent way to ensure everything stays exactly where it was on the previous slide and helps the audience notice exactly what you are changing.
If it helps, put out line numbers on code. Alternatively, you could highlight certain lines of code with an attention focussing comment.
During the talk, use a digital pointer laser pointer to point out particular parts of the code. Often, the mouse pointer disappears and the audience doesn’t know where to look. Use the laser pointer, don’t penalise your audience if they temporarily were distracted.
Plan for the digital audience even if you are presenting in person. Many presenters point out at some code lines during the presentation on the projection or by mouse. This does not get captured in video recordings (not properly, if at all), and is a loss for the quality of your presentation when videos are made available online. Do what you can to use digital pointers or digital pens or highlighters to have all aspects of the presentation captured for eternity.
Use a different colour scheme to highlight the key errors/pitfalls/aspects. Break the monotony for important points. e.g. have a highlighted background to show key errors or show program output.
Highlight conclusions with a different font size and colour that makes them stand out. They are the reason you are presenting!
Have bullet points with minimum words and skip the grammar when making points in natural language. The last thing you want is for the audience to read the slides totally miss what you are presenting. They can only do one of two things – read or listen – as both are language processing activities and only one can happen at a time.
Present data in easy to ingest forms graphs, pie charts, infographics, etc. Use tables sparingly as one does not see the point highlighted. We are not good at number churning!
Use images to highlight points. Word clouds are also images – use them to your benefit. Some general ideas would be to show the before & after, the final application, a screenshot of an error, even a gif. If you can, add a humorous one. Use the cliches to come up with an image assisting your point.
Choose a calm, non-distracting background.
Include a list of references and other reading on the topic. You may not present this slide in the talk but it is a good reference for the audience for later.
When it comes to presentations, less is more! Do not cram a lot on the slides, stay sparse, highlight the point. You can cover any detail in the talk.

C++20 published!

Better Technical & Code Presentations

It all starts… with the first step

Blog post title