How do you estimate the potential gain of the rare case of a software rewrite that makes sense? You want to differentiate between the two outcomes: - "this is one the best pieces of work I've ever done" - "we tried our best; I wished we knew better from the start"
-
-
If the gap was more narrow, there would be little value in trying to figure out how to scale the compiler up and down. But the potential win is big enough that you know upfront it's worth the effort.
-
And the key here is that it gives you a clear objective: you have a very simple setting and a large gap to close. You keep going until you closed the gap or you have a good story for why it can't be done. I find it better for morale than profiling which is shooting in the dark.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.