> This is super hilarious for code paths that try and hide network hits, such that you don't see that that loop is doing a network call per iteration. True st

> This is super hilarious for code paths that try and hide network hits, such that you don't see that that loop is doing a network call per iteration. True story: once I worked on a C++ project with a very ambitious junior developer who liked to portray himself as the local authority in performance and code quality. That junior developer once blocked a PR alleging performance problems because a function call was passing strings by value instead of moving them. Except that function call was only called once per run, and its responsibility was to make 1+n calls to a REST service. Whenever anyone complains about performance, ask for benchmarks. Odds are, even if they are technically right they are still wrong.