-
Notifications
You must be signed in to change notification settings - Fork 15
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
2 changed files
with
58 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,53 @@ | ||
# Exercises for the masses | ||
|
||
## History | ||
|
||
Working in C++ around the year 2010 was very exciting. The language was about | ||
to receive some vast new impulses, promising better semantics, performance, … | ||
|
||
In 2016, I was lucky enough to work in an environment that lived on the edge: | ||
constantly following the latest (Microsoft) compiler versions, and writing C++ | ||
programs according to the latest and greatest idioms. | ||
|
||
All of this happiness had to be shared. That’s why my employer, Sioux Embedded | ||
Systems, asked if anyone would be able to create a C++11/14 ramp-up course for | ||
my colleagues. Of course I bit. | ||
|
||
The budget: 5 days of preparation - a challenge for me. It seemed a vast | ||
undertaking, given the fact that I hadn’t been giving training, nothing ‘free’ | ||
could be found. So I decided I would borrow free and open source presentations, | ||
and create exercises myself. But how? | ||
|
||
As it happened, there also was a gap in the knowledge of unit testing | ||
frameworks. So why not kill two birds with one stone? Fond of TDD, I had grown | ||
quite familiar with the googletest framework. So I decided to create a bunch of | ||
failing unit tests that had to be ‘fixed’ using C++11/14 features. | ||
|
||
Since I was to take all my course material from the internet, I thought it only | ||
fitting to give back. So I started creating the course in the open on | ||
https://github.com/xtofl/cpp11training/. | ||
|
||
## Overview | ||
|
||
### Repo structure | ||
|
||
* Presentations | ||
* Exercises | ||
|
||
### Licensing | ||
### Exercise | ||
|
||
## Future | ||
|
||
Meanwhile, 2020, and I have given this training about 5 times. Everytime, the | ||
overall response is: what a great idea to offer us running code in the form of | ||
isolated unit tests. The fun part for me is that whenever someone finds a | ||
mistake, I can kindly ask them to fix it and create a merge request. | ||
|
||
Of course you'll see that some effort went into supporting different platforms: | ||
some audiences require Visual Studio, others are really diverse and have mixed | ||
platforms - which is why the exercises are now built using CMake. | ||
|
||
|
||
|
||
|