Modern C++ Systems & Performance Engineering Bootcamp Certificate

Checkpoint 1: Build a multi-file C++20 command-line or service project with clear interfaces, value semantics and compiler warnings enabled; document the build and dependency boundaries.
Checkpoint 2: Model ownership explicitly: replace unnecessary raw owning pointers with RAII and smart pointers; demonstrate lifetime behavior and eliminate a deliberately introduced leak.
Checkpoint 3: Use templates and at least one C++20 concept to constrain generic code; compare compile-time type safety against an unconstrained version and document failure diagnostics.
Checkpoint 4: Implement a resource-owning type with rule-of-zero where possible; where transfer matters, demonstrate correct copy/move behavior and benchmark avoidable copies.
Checkpoint 5: Create a modern CMake build with library/executable targets, debug/release configurations and repeatable commands; add automated checks or tests for critical behavior.
Checkpoint 6: Add concurrency with std::thread or equivalent standard constructs; identify shared state, prevent a data race with mutex/atomic design, then measure throughput and contention.

Day 1: Define a performance-sensitive problem, workload, constraints and acceptance tests; sketch modules, ownership boundaries, data structures and expected
Day 2: Implement the baseline C++20 application with value semantics, references and clean interfaces; capture compiler warnings, baseline timing and memory
Day 3: Add templates/concepts and refactor ownership with RAII/smart pointers; run sanitizer or equivalent checks and document one lifetime bug found and fixed.
Day 4: Introduce move-aware resource transfer and benchmark copies/allocations before and after; justify where move semantics helps and where it adds no
Day 5: Create the modern CMake build plus repeatable tests/checks; run debug and optimized builds and record any behavior/performance differences.
Day 6: Add a concurrent path, reproduce one synchronization defect or contention issue, then fix it with a correct mutex/atomic design and rerun benchmarks.
Day 7: Publish repo, architecture/ownership map, CMake instructions, test evidence, memory-safety evidence, benchmark report, concurrency analysis and demo