3 ms·
Well, yes, that's a bad way to measure performance. But when I compile something, it's because I want feedback from the compiler and static analyzer about the
by klodolph 13y ago
Well, yes, that's a bad way to measure performance. But when I compile something, it's because I want feedback from the compiler and static analyzer about the program I just wrote. I have a half-dozen parts of the program in short-term memory which I want to consider when seeing the output or the program behavior. If it takes five minutes to compile code, then my short-term memory will be filled with something else by then, like the weather, chores I'm putting off at home, or whatever.
So if you measure how long it takes for engineers/developers to get feedback, you're really measuring how good their tools are, which is a half-decent proxy for engineer performance.