Skip to content

Commit 20045b6

Browse files
committed
Create 'about' document
1 parent 07431ed commit 20045b6

File tree

2 files changed

+58
-0
lines changed

2 files changed

+58
-0
lines changed

README.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,11 @@ Exercises to train your C++11/14/17 (and then some).
66
[![Build status](https://xtofl.visualstudio.com/cpp11exercises/_apis/build/status/cpp11exercises-CI)](https://xtofl.visualstudio.com/cpp11exercises/_build/latest?definitionId=2)
77
[![Codacy Badge](https://api.codacy.com/project/badge/Grade/e1556f3ddf3645fe98d1fb06bf011b1c)](https://app.codacy.com/app/kristoffel-pirard/cpp11training?utm_source=github.com&utm_medium=referral&utm_content=xtofl/cpp11training&utm_campaign=Badge_Grade_Dashboard)
88

9+
## About
10+
11+
This repo is intended as a resource to use during C++ trainings. If you're curious about how it came
12+
to be, take a look at [about.md](about.md).
13+
914
## Getting started
1015

1116
### Linux

about.md

Lines changed: 53 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,53 @@
1+
# Exercises for the masses
2+
3+
## History
4+
5+
Working in C++ around the year 2010 was very exciting. The language was about
6+
to receive some vast new impulses, promising better semantics, performance, …
7+
8+
In 2016, I was lucky enough to work in an environment that lived on the edge:
9+
constantly following the latest (Microsoft) compiler versions, and writing C++
10+
programs according to the latest and greatest idioms.
11+
12+
All of this happiness had to be shared. That’s why my employer, Sioux Embedded
13+
Systems, asked if anyone would be able to create a C++11/14 ramp-up course for
14+
my colleagues. Of course I bit.
15+
16+
The budget: 5 days of preparation - a challenge for me. It seemed a vast
17+
undertaking, given the fact that I hadn’t been giving training, nothing ‘free’
18+
could be found. So I decided I would borrow free and open source presentations,
19+
and create exercises myself. But how?
20+
21+
As it happened, there also was a gap in the knowledge of unit testing
22+
frameworks. So why not kill two birds with one stone? Fond of TDD, I had grown
23+
quite familiar with the googletest framework. So I decided to create a bunch of
24+
failing unit tests that had to be ‘fixed’ using C++11/14 features.
25+
26+
Since I was to take all my course material from the internet, I thought it only
27+
fitting to give back. So I started creating the course in the open on
28+
https://github.com/xtofl/cpp11training/.
29+
30+
## Overview
31+
32+
### Repo structure
33+
34+
* Presentations
35+
* Exercises
36+
37+
### Licensing
38+
### Exercise
39+
40+
## Future
41+
42+
Meanwhile, 2020, and I have given this training about 5 times. Everytime, the
43+
overall response is: what a great idea to offer us running code in the form of
44+
isolated unit tests. The fun part for me is that whenever someone finds a
45+
mistake, I can kindly ask them to fix it and create a merge request.
46+
47+
Of course you'll see that some effort went into supporting different platforms:
48+
some audiences require Visual Studio, others are really diverse and have mixed
49+
platforms - which is why the exercises are now built using CMake.
50+
51+
52+
53+

0 commit comments

Comments
 (0)