I agree and I've seen that; however, the point of the article is that ideally you have rock-solid code and the only sane way to scale is just to add more of the same resources as the codebase is already optimized.

The reason I posted the quote was to answer your on your remark that it isn't a solution - it is close to an ideal solution actually, but not applicable everywhere and at any time (e.g. sloppy/non-optimized code as you pointed out).

Hope this makes sense.