1. If you write CRUD apps, make sure that the database does the heavy lifting.

2. Take note of algorithm complexities, use hashtables as appropriate, and write good hash functions when you start using hashtables/dictionaries.

3. Avoid pointer-heavy datastructures. In high level languages like Java, an object reference is a pointer dereference that can stall the CPU waiting for memory. This is sometimes optimized, but you can’t depend on it. The true zealots call this “data oriented design”.

4. If you write C/C++,rust, or the like, you might want to learn to read assembly. Godbolt.com is a fun way to learn. Note that not all instructions are equally fast: Long division and trigonomic functions are slower than integer adds, even when they are both a single instruction.

5. The next level is probably going for vectorized instructions: SIMD (ARM Neon, AVX). The most original applications can be found at lemire.me: a professor exploring optimizing things like JSON parsing using the latest processor features.

(Sorry for not testing. Chrome-hater)

For all its shortcomings, this was part of the fun, deducing the likely correct answer when you see a word for the first time.

You can also hunt via Spotify. Songs and artists can help you find curated playlists (by other artists or fans) where you discover new artists.

Everynoise.com is also a great start, but these playlists are no longer maintained.

There is also a huge audience of people who want to hear “elevator music” tuned to their activity at hand and do not care about who or what made it. Spotify obviously wants those customers. I don’t mind these people subsidising my hobby, but I hope Spotify will continue to cater to my interest too.

I apply this in testing code. After you write some code, try to think of the absolute minimal test to prove that your code does anything at all without crashing. These are my “oil tank holiday” tests. It is always humbling to see those fail.