This whole argument does not take into account what article and research was about.
It is not about documentation, UI/UX, collaboration, and other skills. Research was only about programming as in "here is specification for task, code it, please". That is what word "programmer" also conveys. Such person should not be concerned about making user experience better, that is role of a designer. Such person should not be concerned about designing code to be extensible, that is role of a software architect.
What you describe is a one man orchestra, which in reality everyone wants because no one wants to pay for architects, designers, managers, separately.
In the end there are folks who can work on multiple things at the same time like ML and some k8s, I do not believe you can describe what they are doing simply as "programming" or them as just "programmers". Yes they are programmers or coders but there is much more to it. Exactly like patio11 was writing in "Don't Call Yourself A Programmer, And Other Career Advice", because you will be seen just as a code monkey and not as that "one man orchestra".
My main argument is we should stick to the definition.
It is not about documentation, UI/UX, collaboration, and other skills. Research was only about programming as in "here is specification for task, code it, please". That is what word "programmer" also conveys. Such person should not be concerned about making user experience better, that is role of a designer. Such person should not be concerned about designing code to be extensible, that is role of a software architect.
What you describe is a one man orchestra, which in reality everyone wants because no one wants to pay for architects, designers, managers, separately.
In the end there are folks who can work on multiple things at the same time like ML and some k8s, I do not believe you can describe what they are doing simply as "programming" or them as just "programmers". Yes they are programmers or coders but there is much more to it. Exactly like patio11 was writing in "Don't Call Yourself A Programmer, And Other Career Advice", because you will be seen just as a code monkey and not as that "one man orchestra".
My main argument is we should stick to the definition.