I liked this comment because it felt immediately constructive and a great starting point to think about if nothing else. One of probably many examples of this list-based approach (for a different technical subject) is "50 Android Hacks" by Carlos M. Sessa. Avoiding common errors makes sense but are even more valuable when the warnings are paired with idiomatic alternative patterns.

https://www.manning.com/books/50-android-hacks