* computers will always run my code fast
* infrastructure problems will not happen
* our team will always have plenty of time to understand my code
* users are not malicious and the libraries I depend on are not malicious
* I will always have to plenty of time to diagnose and fix problems in this code
The author covers some of that.
But you can care about those, and still be a poor programmer: being too pessimistic is problematic. You need to pick your battles and spend your time mindfully.
Now, I have a problem with this:
> Naive programmers think that design means “don’t make functions or classes too long”. However, the real problem is writing code that mixes unrelated ideas.
How do you enforce that policy using a linter? How do you audit a large project for these issues? You can count characters in a line, you can count lines of code in a function or file, and you can count import statements. All those are indicators of coupling unrelated ideas together.