Talk (60 min)

31 August

Keynote: Kate Gregory

The Boeing 737 MAX: When Humans and Technology Don't Mix

Design

Product

Technique

Software Design

In this session, I want to broaden our horizon on having this holistic perspective on our responsibility for sustainability that comes with software development. I will share both ideas about possibilities and examples from companies who make already an effort in implementing this holistic perspective because sustainability becomes more and more a success factor for every company: For finding and keeping both clients as well as talent. Thus, this session is about raising awareness of our contribution to sustainability and understanding the (first) steps we can take to make a difference.


The Planet sends an S.O.S. – Taking Responsibility for our Carbon Footprint

Testing

Architecture

Product Design

C++20 - My Favourite Code Examples

Properties of Unit Tests

Typical C++, but why?

Containers as an Illusion - Part I

Security

How to start a program

Platform

Theory makes beautiful programs; or MC/DC in gcc

Embedded

In reality, for safe, secure, and performant systems the opposite is true and unsigned integers should be the default type for representing integer that cannot have negative values. This goal of this presentation is to provide an irrefutable argument supporting this assertion and put an end to the madness.

Signed Integers Considered Harmful

Language

Making sense of "volatile"

Auto-testing for situational awareness

In the meantime, it has been largely clarified what we can expect with the upcoming standard. Major deviations from it are unlikely to happen, but minor things that are already in the pipeline may still be added in the coming months.

I will present the following main points:

1) what was the Bold Plan that guided us through three years of development?
2) what is already included in the draft and what is likely to be included?
3) what could unfortunately not be finished in time?
4) which changes also affect C++20?
5) where do the implementations of the major compilers stand in terms of implementation?
6) show a few highlights from C++23 in code examples


A Preview of C++23

Zephyr RTOS: Software power tools for constraint devices

Tools

Reprogramming Binary Programs

Error handling in C++: as easy as "use exceptions"?

42 Silly Ways to say Hello in C

Trying to get people to a place where they are a productive junior developer in C++, and have modern C++ habits is a challenge. In this talk we explore learning C++ as a programmer, and choosing what to skip and what to teach.

The Floor is Lava, trying to teach C++

Containers as an Illusion - Part II

Complimentary food and drinks will be served. There will also be a C++ Quiz, hosted by Anders Schau Knatten.

Half-Day

NDC Party (Food, Drinks Quiz)

For many developers Type Erasure is superior to inheritance with respect to dependency management. And indeed, it has proven itself to be a powerful design pattern, helping to significantly reduce coupling between software entities. Unfortunately, there is no language support for Type Erasure (yet) and many shy away from the seemingly complex implementation details.

In this talk I will give advice on the different ways of how to implement Type Erasure. I’ll start with two very simple, ~20 line implementations for owning and non-owning Type Erasure Wrappers. But I’ll also go into detail about different performance optimization strategies, such as the manual implementation of virtual functions and the Small Buffer Optimization (SBO). After this talk, attendees will know everything to realize and utilize Type Erasure in their own code bases.

Breaking Dependencies: Type Erasure - The Implementation Details

Some parts of it are controversial, but one point is for certain: It was written in 2008, when C++ was very different from what it is today.

Some people took up the gauntlet of modernizing these guideline, first through the AUTOSAR initiative, then through reviving a MISRA C++ working group. After blood, sweat and tears, this group is about to publish a new version of MISRA, MISRA C++202x.

In this talk, I will take you through some of the new guidelines of MISRA, explaining how they came to be, what they try to achieve, how they evolved since 2008, and how you can write safer code without giving up an unreasonable amount of the expressiveness and power of C++.

MISRA C++202x: It ain't your grandpa's MISRA any more

Martin Fowler once wrote that high-quality software is actually cheaper to produce than low-quality software. We agree with that sentiment, and we warmly welcomed the C++ Core Guidelines when they were introduced in 2015. Research and surveys conducted in the C++ Community consistently demonstrate the popularity of the Clang family of tools, as well as the growing demand for static analysis to be added to code editors. In this talk, let’s explore the current state of static code analysis in C++.

Code Analysis++

Existing modern languages already provide an excellent developer experience: Go, Swift, Kotlin, Rust, and many others. Developers that can use one of these existing languages should. Unfortunately, the designs of these languages present significant barriers to adoption and migration from C++. These barriers range from changes in the idiomatic design of software to performance overhead.

We decided to experiment with a different direction: a successor language approach. It is designed around interoperability with C++ as well as large-scale adoption and migration for existing C++ codebases and developers.

So we've started building the Carbon Language: an experimental successor to C++.

That said, we really *don't* know what comes next for C++. We don't even know whether Carbon should be part of what comes next. We're just getting started with the long process of designing this kind of successor, and haven't even finished a compiler. We still need to finish the design, implement it, see if it works, and see if the C++ community is interested in this direction.

This is why we're here. We need you and the rest of the C++ community to help us build and shape Carbon into something that addresses all of our needs. And we need all of you to help evaluate whether it is the right direction. We're here to ask you to join us as we get started on an exciting experiment, and a long journey.

To find out more, check out our project: 

https://github.com/carbon-language/carbon-lang

1 September

C++: what comes next?

In this talk I will show you how to get started with Yocto, first using QEMU to create an emulated target board, and then using a Raspberry Pi. I will describe the basics of Yocto: Distro, Machine, Image. I will talk about Bitbake and bitbake recipes and I will show how recipes can be gathered together into layers. If you want to get a head start with Yocto Project and embedded Linux, this is the talk for you.

Getting started with Yocto Project

Linux

Neotron - why write a brand new ‘DOS’ for Arm in Rust?

Identifying Common Code Smells (In C++)

Generating Generators

Learning Rust the wrong way.

Rust for the C++ Developer

Surviving a chip shortage

Contemporary C++ in Action

Package management in C++

Thinking Erlang in a connected world: What 12 years of experience has taught me.

An Introduction To Floating Point Math

5 Years Of Teaching C++: A Retrospective

C++ Lambda Idioms

A lock-free atomic shared_ptr

Analysis of Real World Apps with Frida

How we made Zivid Two - our 2nd generation 3D machine vision camera for robotics

This talk tries to give a balanced overview of the Singleton pattern. I will show the cons as well as the pros and will demonstrate how to properly deal with Singletons to overcome the major disadvantages. In particular, I will show how to implement Singletons such that dependencies to implementation details are avoided, code can be easily changed and full testability is given.

The Singleton Pattern: Anti-Pattern or Solution?

I will build vocabular types describing basic components of the problem, and use the standard library to build a generic library. The talk is a case study of how well designed generic code can be used to many purposes.

 Lightning Updates

Based on over 20 years of experience I will give you some pointers about what embedded means and the way that we develop in this environment.

I will talk about the underlying hardware: the System on Chip (SoC) and how that is packaged as a System on Module (SoM), or a Single Board Computer (SBC), or into a custom designed board. For each target, we need the four basic components of an embedded Linux system: the toolchain, the bootloader, the kernel and the root filesystem. Then, on top of that you need the applications that are going to turn it into a world-beating gadget. That may include graphics drivers to control a touch screen, network interfaces to connect to a cloud backend and databases to store structured data. There may even be real-time control tasks. Finally, I will consider how you combine the open source base operating system with your own proprietary code

NDC { TechTown }

Agenda

09:00 - 10:00 (UTC+02)

Keynote: Kate Gregory

Kate Gregory

10:20 - 11:20 (UTC+02)

C++20 - My Favourite Code Examples

Nicolai Josuttis

How to start a program

Anders Schau Knatten

The Planet sends an S.O.S. – Taking Responsibility for our Carbon Footprint

Jutta Eckstein

Signed Integers Considered Harmful

Robert Seacord

11:40 - 12:40 (UTC+02)

A Preview of C++23

Daniela Engert

Reprogramming Binary Programs

Ole André Vadla Ravnås

Auto-testing for situational awareness

James Westfall

Theory makes beautiful programs; or MC/DC in gcc

Jørgen Kvalsvik

13:40 - 14:40 (UTC+02)

Error handling in C++: as easy as "use exceptions"?

Vitaly Fanaskov

Containers as an Illusion - Part I

Michael Kerrisk

Properties of Unit Tests

Arne Mertz

Zephyr RTOS: Software power tools for constraint devices

Eirik Midttun

Balaji Srinivasan

15:00 - 16:00 (UTC+02)

Typical C++, but why?

Björn Fahller

Containers as an Illusion - Part II

Michael Kerrisk

MISRA C++202x: It ain't your grandpa's MISRA any more

Loïc Joly

42 Silly Ways to say Hello in C

Olve Maudal

16:20 - 17:20 (UTC+02)

Breaking Dependencies: Type Erasure - The Implementation Details

Klaus Iglberger

Code Analysis++

Anastasia Kazakova

The Floor is Lava, trying to teach C++

Patricia Aas

Making sense of "volatile"

Inge Fredriksen

17:20 - 21:00 (UTC+02)

NDC Party (Food, Drinks Quiz)

Anders Schau Knatten

18:00 - 19:00 (UTC+02)

The Boeing 737 MAX: When Humans and Technology Don't Mix

Kyle Kotowick