Is the power of. net making programmers cheaper?

I just saw a post about C #. Net for one year. I found that the base is actually poor. Here is an example:
Executenonquery returns the number of affected records. Because the result does not understand the specific meaning of the returned value, the results are modified and judged repeatedly after the test.
Yes, thanks to. Net's strength, programmers do not need to have strong programming language capabilities, nor have strong interface design capabilities, or even simple engineering structures.
You only need to create a. Net project, drag the control, and write events. So now the programmer's threshold has become very low, and it will take 2 to 3 months to enter a training institution.
Followed by the project. Of course, the corresponding treatment is much cheaper, and many colleagues say they are "It migrant workers ".
Of course, this is not just the strength of the development platform. For example, software engineering is becoming increasingly mature, software reuse is also growing, and many things have been used by our predecessors,
Now, you only need to make a few changes to meet the requirements. Of course, you will not be dumb to develop again. Even if you want to develop, the company cost and customer delivery time are not allowed (unless you are the boss yourself, this kind of boss is probably not long enough)
Everything is evolving. The development platform is powerful and greatly reduces the workload of manual work. This is a manifestation of progress. If we can make software development more like pipeline work, it will be even more progressive.
So what should our programmers do? I have been thinking carefully for a long time. It doesn't mean that we don't want to study technology or lay a solid foundation. But when the software develops into a "Software Engineering", the programmer is not called a programmer or a "software engineer", so we don't just write code, but write this project (engineering architecture) and manage projects. Let's give an example of clothing. At first, a person made a dress and bought the cloth, cut it by himself, made it by himself, and finally delivered it. Later, he received an apprentice and made it hard, the apprenticeship was simple, and later he received many apprentices. Each apprenticeship learned differently. Some learned to make sleeves and some people made collars ..., it only assigns tasks. It doesn't matter whether the clothing company's "he" doesn't make clothes till now. He just needs to make the production process smooth. In the same way, the title of "programmer" has not changed since software was developed. However, his role and position have changed. So how do programmers learn in the future, or how much they learn? The focus is on your positioning of yourself as a programmer or your future positioning, only when you understand where you are can you know what you are doing, what you should do, what you should learn, and what you should learn and do in the future.
All of the above are personal opinions. It may be true or wrong.