A programmer's honest review of Clean Code

Read it, but argue with it as you go. The naming chapter alone is worth your time, and it changed how I review pull requests. Some of the advice on tiny functions goes too far, though, and a few of the worked examples end up harder to follow than what they replaced.

I think of it as a book for your second or third year of work. Before that you don't have enough bad code of your own to recognise what he's talking about. After that you know which parts to ignore.