Erase it and do it iteratively like any sane person! Kidding aside, I'm more talking about the kinds of large procedures common to C++ codebases. These involve

Erase it and do it iteratively like any sane person! Kidding aside, I'm more talking about the kinds of large procedures common to C++ codebases. These involve many sequential state changes which leave lots of opportunities for not initializing things and the like when the right set of conditions are met. The more paths available through this kind of code the more likely it becomes we'll create a bad one and fail to anticipate the conditions which trigger it.