Sure, but the article seems to be putting the expert programmer in the role of product owner. That is possibility in some organizations (and it's a good way to burn out that expert).
However, in others, it is the product owner, product or program manager or the like who has the responsibility and accountability for setting the work agenda and approving it. If the expert programmer goes rogue and ignores their wishes, this will create a bad working relationship. Since product owners tend to be closer to middle/upper management guess who gets the blame? That's when the expert developer gets put on a "personal improvement plan" because they aren't a team player and fired soon after if they don't leave on their own accord.
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.
Sure, but the article seems to be putting the expert programmer in the role of product owner. That is possibility in some organizations (and it's a good way to burn out that expert).
However, in others, it is the product owner, product or program manager or the like who has the responsibility and accountability for setting the work agenda and approving it. If the expert programmer goes rogue and ignores their wishes, this will create a bad working relationship. Since product owners tend to be closer to middle/upper management guess who gets the blame? That's when the expert developer gets put on a "personal improvement plan" because they aren't a team player and fired soon after if they don't leave on their own accord.