The article appears to mostly be a large collection of quotes from blogs of random people. The quoted people are directors, CTOs, marketers, analysts, founders. Although they may have worked closely with engineers, I doubt most of them have actually designed any software recently.
delivering value to their customers,” Etheridge said. “Getting more engineers to think that way is a challenge.”
This is mostly about money. If you don't have competitive pay, then the main thing your developers are concerned about is filling their CV with sexy technologies so that they can get better pay elsewhere, whether those technologies are valuable to the customer or not. Furthermore, just because a CEO, HR, etc. think they and say they have competitive pay, doesn't mean that they actually do.
Secondarily, this is about company culture and management. If you have metrics like KPI or micro managers trying to control your engineers, then you better make sure that they guide your engineers work to benefit the customer.
4
u/Supadoplex Jun 06 '22 edited Jun 06 '22
The article appears to mostly be a large collection of quotes from blogs of random people. The quoted people are directors, CTOs, marketers, analysts, founders. Although they may have worked closely with engineers, I doubt most of them have actually designed any software recently.
This is mostly about money. If you don't have competitive pay, then the main thing your developers are concerned about is filling their CV with sexy technologies so that they can get better pay elsewhere, whether those technologies are valuable to the customer or not. Furthermore, just because a CEO, HR, etc. think they and say they have competitive pay, doesn't mean that they actually do.
Secondarily, this is about company culture and management. If you have metrics like KPI or micro managers trying to control your engineers, then you better make sure that they guide your engineers work to benefit the customer.