Yet another example of someone mixing the concepts of scientist, engineer, and technician in the computing world.

You wouldn't hire a food scientist to control and feed the machines that produce the bread in an industrial bakery, or even to design and build that production line. Producing code is not as closely related as one might think to the science that leads to the algorithms and design patterns that underscore the languages and frameworks that enable the tools and techniques ultimately used by those who produce code.

The sooner all concerned (me, you, academics, entrepreneurs, employers) settle on a suitable terminology for what it is that computer scientists, software engineers, and developers need to learn to do what they do, the sooner we can get past this type of article.