C++, performance and the decisions that make systems better. For those getting started — and those who never stopped asking why.
Find your next read
01 / FEATURED Calling a C++ function is easy. Knowing who owns the memory after it returns is the whole job. CLR, C++/CLI bridges, P/Invoke, marshaling, and lifetime contracts.
Read the articleA game without progression is a demo. Here is how Code Royale earned its gamification layer — daily missions paid out server-side, a streak you can actually lose, XP that means something, and the world ranking I just rebuilt.
↗A 1v1 real-time coding battle is not a CRUD app. Authoritative WebSocket state, a countdown that survives background tabs, matchmaking that never leaves you waiting — the engineering behind a game where the clock is part of the contract.
↗"std::move" is a cast, not an action. What rvalue references actually bind to, why moved-from is "valid but unspecified," and where the copy you thought you eliminated silently stays.
↗How RAII actually works: constructors that acquire, destructors that release, and the unwinding guarantees that make exceptions safe. Plus where RAII breaks.
↗Concurrency organizes progress. Parallelism allows simultaneous work. Explore the difference in the drawing — then in the code.
From the idea to C++ ↗Fundamentals, ownership, concurrency and memory. Build the knowledge to make better decisions.
Open the full learning path ↗