I loved reading through this even as someone with a chunk of years in the industry. It puts pen to paper on a lot of topics that we usually deem "obvious".
You can read it for free online here: https://github.com/braydie/HowToBeAProgrammer
You can read it for free online here: https://github.com/braydie/HowToBeAProgrammer
In my experience, I've found that:
(1) good "self documenting code" is typically written by programmers who care enough about documentation to write at least a high-level description of what their code is trying to achieve, what problems it is trying to solve.
(2) programmers who swear by "self documenting code" usually write code that is anything but self-documenting. Their output is usually so gloriously complex that nobody apart from them can easily read and understand their code.