From the article: So here’s the punchline: if you want to be a good programmer then learn a technology and language agnostic formalism. No. If you want

From the article: So here’s the punchline: if you want to be a good programmer then learn a technology and language agnostic formalism. No. If you want to be "a good programmer", then learn how to define the problem for which you are tasked to solve. The technology is irrelevant. The "language agnostic formalism" is irrelevant. Unless a person/team knows what must be done, then the rest really doesn't matter. Techniques which help to elicit repeatable delivery certainly are worthy to learn, even to advocate for. But without understanding what is needed, what use are they?