Get the latest tech news
Optimizations That Aren't
We all like it when our code is fast. Some of us like the result, but dislike the process of optimization; others enjoy the process. However, optimization for the sake of optimization is wrong, unless you’re doing it in your pet project. Optimized code is sometimes less readable and, consequently, harder to understand and modify; because of that, optimization often introduces subtle bugs.
If possible, it should be covered by tests; otherwise one can resort to saving the results that the code produces, i.e. a data array for a particular input or a screenshot. There are two absolutely crucial things here - make sure that the code still works, and have proper profiling before- and after- results. As you can imagine, this makes all functions from the cache linear in terms of scene object count, and thus the whole export process quadratic.
Or read this on Hacker News