Discourse about best practices in coding starts to make a lot more sense when you understand that 95% of it is built on the assumption that every single person who interacts with the code in any capacity whatsoever will be a dedicated hobbyist.
Like, yes, I'm sure the approach you're advocating is wonderfully self-documenting when the person looking at the code has decades of experience with the language in which it's written, and sufficient subject matter expertise regarding the processes it's implementing that they can intuitively draw a line between what the code is doing and why it's doing it, but how about when the person looking at it has no relevant subject matter expertise and no prior experience with the language in question, having been given the task of revising the code you left behind twenty years ago simply because they're the only one currently on the team who knows what a variable is?
Best practices are going to look pretty different depending on which of these maintenance scenarios you're assuming is typical, and statistically, the second one is a heck of a lot more likely!
