alright, you probably already have these, but bare minimum top 5: 1. testing automation 2. version control systems/collaboration workflows 3. OOP basic conceptual shit 4. functional style basic conceptual shit 5. what is the real actual first thing about optimization?
-
-
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.