3 ms·
Amdahl's law, by far. I find myself explaining it on almost a daily basis. I work on big enterprise software and our junior engineers tend to enjoy optimizing a
by cityofdelusion 8y ago
Amdahl's law, by far. I find myself explaining it on almost a daily basis. I work on big enterprise software and our junior engineers tend to enjoy optimizing a piece of some system, without realizing that the speedup of the system as a whole will be negligible.
I find performance / architecture stuff in general to be useful to know, along with having an intuition for orders of magnitude. Too much needless complexity exists in enterprise CRUD web apps for a 1.01x speedup.
- thermodynthrway 8y agoI've found the speed of the framework generally matters more than what you do with it for the same reason. The size of the framework often dwarfs any application built with it these days. We have a huge project in Spring Boot that crawls along, and a newer one in Dropwizard that's so fast we could support 1000x our current traffic. Funny because they both use Hibernate and JAX-RS to do roughly the same thing
- jjeaff 8y agoI can relate to that. I just spent 2 weeks going down a rabbit hole trying to optimize a recursive algorithm to be able to calculate some values quickly. I finally gave up and returned to the slow method but cached the results. Now we just warm the cache at night when usage is low. Put it together in a day. Wish I had just gone this route from the beginning.
- copperx 8y agoThe term for that is memoization, for googling purposes.