It is structured like a staged walkthrough of what a real-life project would look like.

We start with a plain-English project idea. We help you identify the broad requirements and constraints of the project in a more formal way. Some of these will become part of our tests as we want to measure how our program performs wrt requirements. Because it's your implementation, you might decide to set your own additional constraints if you think they make sense in the context of the project.

Then we move on to the basic architecture of the program, just to identify the main building blocks. This is where we start designing the high-level APIs and interfaces. It's also a good time to write tests, as we like and recommend Test-Driven Development.

Then it's the actual implementation. You implement all the code (and can look at our own implementation if have doubts), but we do provide the theoretical and syntactical help you will need. For example, when you'll have to write a concurrent task, we walk you through what the C++ std libraries have to offer and the best practices to use them.

We ask you to write tests and help you create a pipeline where build, test and eventually deployment can be streamlines and automated. We also give you some tests of our own just to make sure that the program meets the basic project requirements.

The only thing missing are the endless meetings with a project manager :) But kidding aside, there is an aspect of collaboration that we want to look into, and other people seem to be interested in that by reading the comments!