Even if the suggestions are a bit too generic, they might click for someone some time after they've read it. It also helps validate some things that less experienced programmers might be doing but aren't sure are the best things. I for example found that some things I seem to be gravitating towards are mentioned, which will hopefully allow me to focus on them and grasp them better in the future.
I might be, being miss-interpreted as dismissing this article.
They are definitely good points, and doesn't hurt to read them.
I think all the points are valid.
Maybe I was just contemplating how experts sometimes 'summarize' their knowledge, condense it, but in the process of trying to be succinct, becomes itself un-fathomable, generic.
I suspect that the unfathomable nature of condensed knowledge arises from the fact that there is simply no shortcut to expertise. You must earn it through experience.
Someone with a similar level of experience to the author may well have the right foundations to draw on such that a condensed expression of an idea resonates well. Others may only get a "seed pearl" to help shape how they view their past and future experiences. And some might be able to recognise that there is wisdom there, but not be able to relate it to their own understanding at all.
Without any relevant experience, it's just words devoid of much meaning.
Many of these suggestions made me remember my own experiences, some where I intuitively followed them and some where I did not. Reading this write-up made me realize their value and will hopefully remind me that I need to do these things more often.
As someone who is not an expert but tries to gain wisdom from past experiences, it helps me to see where my intuitions might have been right or wrong, even if I may not get the point right away.
and
For A new, non-expert, these suggestions might be too generic, too high level, broad. They wont grasp the point.