theres wisdom in what you advise, but I think theres one glitch with the wording which might cause a backlash. what you say a "developer" should be doing/thinking, is really not what a software engineer does or should be doing. you're talking about product development. in a small enough shop where a few people must where all the hats, sure one person might be wearing the product development and software engineering hats. in a larger, more established company, they will not.
the vast majority of folks in software engineering should not be thinking in terms of user exitement, or market value or brand positioning etc.
if I were a solo indie entrepreneur/engineer who had to wear all the hats I couldnt delegate to others? heck yes I should follow your advice.
marketing, product design and UX are all incredibly important. but they are not the responsibility, or anywhere in the top concerns, of a software engineer. for the business overall? heck yes
the vast majority of folks in software engineering should not be thinking in terms of user exitement, or market value or brand positioning etc.
if I were a solo indie entrepreneur/engineer who had to wear all the hats I couldnt delegate to others? heck yes I should follow your advice.
marketing, product design and UX are all incredibly important. but they are not the responsibility, or anywhere in the top concerns, of a software engineer. for the business overall? heck yes