Why do Senior C++ Engineers use size_t over int?

Explains why C++ developers should use size_t instead of int when iterating over vectors with index-based for loops. Covers the type mismatch between int and the return type of vector::size(), the risk of implicit casting truncating large vectors, and the unsigned integer wraparound pitfall when decrementing size_t below zero. Demonstrates the correct pattern for both forward and reverse iteration using size_t.