inexperienced developers are unable - or just rarely - ask themselves the question: "is the current performance in the right ballpark of where it should be?"

inexperienced developers are unable - or just rarely - ask themselves the question: "is the current performance in the right ballpark of where it should be?" here it's obvious - muratori took one look at that thing and just knew that "no, 2-3 fps is definitely, completely off". i, too, had a couple of those moments where i got my hands on some code and thought: "that just can't be right" and then found O² algorithms, byte-by-byte io copy routines, database abuse or duplicated work. if you don't have the rough reference points of what should be right, you often just don't question correctly working code.