That's really a question for Google or Stack Overflow.

One source would be: https://www.oreilly.com/library/view/code-complete-2nd/07356...

They are 100% doing it. A lot of really bright people work on the engines/compilers.

The problem is telling individuals to focus on optimization.

Let's use javascript as an example. Say you need to transform an array. You can use `.map` or a `for` loop in javascript.

You see a lot of articles like this https://dev.to/henryjw/array-map-much-slower-than-for-loop-5... that say a `for` loop is faster. And sometimes it's true.

By the logic of the original article, you should hyperoptimize your code. The problem is. If everyone writes `for` loops instead of using `map`. When map eventually becomes more efficient there's all that garbage code out there that has to be refactored.

Ignoring the problems associated with benchmarking - this for example claims map now being faster than for loops. https://leanylabs.com/blog/js-forEach-map-reduce-vs-for-for_...

It comes down to return on effort. We only have so much effort to put at solving this problem. You maximize your return on effort by having a clear separation of responsibility. In this case the individual's responsibility is to write code to the latest spec. The institution's responsibility is to make the code written as efficient as possible.

A single website saving .000000001 ppm of carbon (exaggerating) is just never going to be worth the effort. But a compiler improvement on all websites running javascript. Now that's totally worth it.

Further reading behind this logic: https://www.goodreads.com/book/show/3828902-thinking-in-syst...

https://stackify.com/premature-optimization-evil/

Code Complete (chapter 25.2) https://www.oreilly.com/library/view/code-complete-second/07...

Depends on what you're into, but from the database angle:

Learning SQL is a really excellent intro, and probably covers the majority of what your average developer is going to ever need to know about SQL ( http://shop.oreilly.com/product/9780596520847.do )

SQL and Relational Theory gives you more background on relational theory - basically gives a more academic background for existing practitioners of SQL. Date is pretty dry author with a few hangups, but it's largely good solid stuff ( http://shop.oreilly.com/product/0636920022879.do )

Oracle Essentials is a good solid introduction to Oracle, and gives a useful bit of background on how database management systems work ( http://shop.oreilly.com/product/9780596514549.do )

For other subjects:

Code Complete needs little introduction ( http://shop.oreilly.com/product/9780735619678.do )

I've only just started reading Version Control with Git, but it seems pretty good so far, and is well-reviewed ( http://shop.oreilly.com/product/9780596520137.do )

Available for purchase at Oreilly's site: http://oreilly.com/catalog/9780735619678/

If you create an account, they have a buy one get one free ebook deal running all the time.