Ehh. A lot of things in the skillset of a capable real-world programmer have little to do with actually writing code, which is the whole point of the book. As can be trivially gleaned by taking a cursory look at the table of contents. And answering the question "how to write better code" with "write more code" is about as helpful as advising a depressed person to just go out and have fun.

Saying you'll be a better programmer if you just write code is like saying you'll be a better mathematician if you just write more math.

My math skills improved the most when I stopped obsessing over studying the right things, or finding the right textbooks, and just constantly solved problems.

Being a mathematician and solving already-theoretically-understood math problems are two things that often don't have a lot of overlap.

Yeah fair.

It’s another way to describe practice. Which is correct but not the most compelling of arguments.

Do you have any examples of methods that will get you there more effectively than practice in any discipline? Because I honestly can't think of anything.

Boys; I've got this:

Because the chapters for instance under 2.0 are absolutely spot on.

Edit:

The rest are absolutely as well. Are what you say? Spot on!