Many developers can be very good with double duty. The development can be much faster if developers know about the business, otherwise, developers will depend on the business requirements, in my experience, most businesses have many logic issues. Many of the business put visual in front of logic, they do not want to see a complicated flow chart.
In my personal experience, the business ask designers to make up some static HTML or powerpoint slideshow, then ask developers to "just plug your code in". I also have seen 1000+ pages of requirements with a lot of words but no logic.
Normally the business does not like to deal with developers because we are not "fun" people. They like to find some "messengers", to become a messenger, this person needs to be "fun" and "positive" with a very basic understanding of development. The worst case is those messengers might get over developers and start to tell the developer how to do their job.
My point is, it will be great for both the business and other developers if this person can do both jobs. However, most business cannot understand this or just simply do not want to do this, especially when the middle-level managers like to keep their "fun" job.
It is hard to find a job that everyone you work with is professionals, especially those days, seems everyone just as "valuable" as developers. But if you are the lucky one, do not leave.
I would add some to your list: Understand one great developer worth more than many so so developers. Understand many developers are actually doing the business job.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Many developers can be very good with double duty. The development can be much faster if developers know about the business, otherwise, developers will depend on the business requirements, in my experience, most businesses have many logic issues. Many of the business put visual in front of logic, they do not want to see a complicated flow chart.
In my personal experience, the business ask designers to make up some static HTML or powerpoint slideshow, then ask developers to "just plug your code in". I also have seen 1000+ pages of requirements with a lot of words but no logic.
Normally the business does not like to deal with developers because we are not "fun" people. They like to find some "messengers", to become a messenger, this person needs to be "fun" and "positive" with a very basic understanding of development. The worst case is those messengers might get over developers and start to tell the developer how to do their job.
My point is, it will be great for both the business and other developers if this person can do both jobs. However, most business cannot understand this or just simply do not want to do this, especially when the middle-level managers like to keep their "fun" job.
It is hard to find a job that everyone you work with is professionals, especially those days, seems everyone just as "valuable" as developers. But if you are the lucky one, do not leave.
I would add some to your list: Understand one great developer worth more than many so so developers. Understand many developers are actually doing the business job.