This would in most cases be the product manager and designer / product team's responsibility. "the success of being a developer" has more to do with getting things to work in a most efficient, correct, scalable and easy to use manner, as fast as possible, but still avoiding the temptation to cut corners and don't follow best practices, as these will come back and bite you hard.
While it wouldn't necessarily be the Developer's responsibility... having empathy for the user will generally be necessary for the "easy to use" portion of your statement.
This would in most cases be the product manager and designer / product team's responsibility.
"the success of being a developer" has more to do with getting things to work in a most efficient, correct, scalable and easy to use manner, as fast as possible, but still avoiding the temptation to cut corners and don't follow best practices, as these will come back and bite you hard.
While it wouldn't necessarily be the Developer's responsibility... having empathy for the user will generally be necessary for the "easy to use" portion of your statement.
Sure, but if so, you still have to be able to connect those dots. That’s pretty much what it boils down to in the end.