A free monthly newsletter with deep dives into modern C++: language fundamentals, object lifetime, design, and build systems.
Each issue includes a concise PDF guide (10–15 pages) with clear explanations, real-world examples, and diagrams — not fragmented tips.
One email per month. No spam. Unsubscribe anytime.
C++ can be confusing — especially when you learn it in fragments.
Most articles on the internet solve one narrow problem without providing enough context.
That approach may help in the moment, but it doesn’t build a solid foundation for long-term growth.
That’s exactly why I created this monthly newsletter.
About me
I’m Nikolai, a C++ developer and author writing about modern C++ software development practices.
I create concise, practical materials for developers who want to stop fighting C++ complexity and start using the language the way it was designed to be used.
What makes this newsletter different
This is not a collection of short tips that are forgotten five minutes after reading.
Each monthly issue includes:
- Not short tips you forget in 5 minutes
- One focused topic per issue
- 10–15 page PDF with diagrams and real code
- Principles you can apply beyond a single example
The goal is not memorization, but understanding.
Topics I cover
Although the newsletter is rooted in C++, it also covers the tools and concepts that matter in real-world development.
Issue #1 — Modern CMake fundamentals
The first issue focused on modern CMake and covered:
- The core idea behind modern CMake
- Why global configuration breaks your project
- How to define clean, isolated targets
- Before/after examples of incorrect vs correct CMake
- Usage requirements explained:
PUBLIC,PRIVATE,INTERFACE
Issue #2 — C++ object lifetime and ownership
The second issue dives into one of the most error-prone areas of C++:
- Constructors define invariants
A well-designed constructor must leave the object fully initialized.
If a type can exist in a “half-ready” state, bugs are inevitable. - Copy vs move semantics
Copying duplicates ownership.
Moving transfers it and leaves the source in a valid-but-unspecified state.
Using an object incorrectly after a move is a common source of subtle bugs. - Special member functions and ownership
If a class manages a resource, default copy/move/destruction may be wrong.
This is where RAII and the Rule of Five stop being theory and start saving you from real bugs.
More issues planned on object design, build performance, testing, and real-world C++ architecture.
If you want to build a clear mental model of C++ instead of collecting isolated tricks, this newsletter is for you.
👉 One issue per month. No noise. Deep dives only.
If you want to build a solid mental model of C++ instead of collecting isolated tricks, this newsletter is for you.
One issue per month. Deep dives only.