This list is fine for what it is but if we want to be meta and go a level higher, we would categorize the author's perspective as "programming is a means to an end".

Therefore, the article is really "21 Ideas for Software Developers Who are Paid to Solve Clients' Business Problems".

Yes, that can be a valid perspective but if we already agree with that as a base premise, the 21 ideas are common sense. It's tautology.

However, there is another perspective to programming which is that programming is NOT the means to an end. For some, the programming is itself the enjoyable activity. Programming is how some may self-actualize[1] and express themselves. In this case, the sentiments are reversed: any business and monetary value from programming is a side effect and the money becomes the means to an end to fund more programming.

Yes, the programming-is-just-a-tool perspective outnumbers the programming-as-artistic-expression but that doesn't change the fact that both exist. You just have to be aware that if you're a "programmer-artist" you will not fit in culturally at a Big Company that requires "boring software deliverables" from you.

[1] https://en.wikipedia.org/wiki/Maslow%27s_hierarchy_of_needs