Accelerated C++: Practical Programming by Example

Let requirements drive abstraction, rather than first memorizing language parts

§5.3 Using iterators instead of indices; §6.3 Classifying students, revisited; Chapters 11–15 resource types and handles

This book first lets the reader complete visible tasks with string, vector, and algorithms, then explains how to construct resource types. Student classification runs through several implementations; what changes is not the meaning of “the student passed,” but whether the input is retained, when iterators are invalidated, and how many times elements are moved. remove_if especially reveals the boundary between algorithms and containers: it can overwrite existing elements but does not own the container's size; erase is what ends the lifetime of the trailing elements. A modern tutorial can replace old adapters with lambdas, but cannot omit this layer of contract. The later Vec, handle, and picture-inheritance material continues to answer questions of representation and ownership; it is suitable for analyzing responsibilities but is not a production implementation that should be copied directly. Exception paths and polymorphic deletion still require independent review.