> Because of that, the first step on the road to fast programs is to measure!

> Making an operation that accounts for 1% of the overall runtime 100% faster is far less effective than making something that accounts for 50% of the runtime10% faster.

Currently dealing with a slow DB and a team of "engineers" who have just NOT internalized the above. It's been very demoralizing.

https://www.youtube.com/watch?v=r-TLSBdHe1A

And who knows, maybe they'd even be interested in using coz afterwards:

https://github.com/plasma-umass/coz