Could you expand on point 5?
-
-
-
sure. I have two things in mind for this one but they're interrelated. The first thing is riffing on the famous Don Knuth quote "premature optimization is the root of most evil in programming". so the real actual first thing about optimizing code is to make sure you need to.
-
you need to optimize your code if and only if: - this code is really your bottleneck - this code actually solves your problem (from the perspective of the business or the end user) - this is a better use of your resources than throwing hardware at the problem
-
the second thing I have in mind is that optimization is ENTIRELY about measurement and if you can't measure your code's performance in a meaningful way any attempt at optimization is futile at best and potentially destructive
-
so this means have a real performance benchmark that matters in the situations where your performance issue is really a problem. a lot of on-paper benchmarks do not accurately measure the performance of the code in real situations where the code is running.
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.