the larger the code for something gets, the potential for unintended interactions increases exponentially. sometimes optimizing means to remove those unintended interactions, but sometimes you find ones that help and you then try to implement (“it’s not a bug, it’s a feature” type of thing). sometimes those unintended things are quirks of the language they are using, or for consoles if there is specific hardware the developers learn how to exploit as they gain experience. an example, in C++ the operation “i++” takes 2 or 3 processor cycles more than “++i”. a small amount to improve, but if you need i to count to a million, that’s 2-3 million processor cycles saved.
Latest Answers