Part of the problem is that many software developers work in organisations where that kind of information - dollars saved or made, time saved, steps reduced - i

Part of the problem is that many software developers work in organisations where that kind of information - dollars saved or made, time saved, steps reduced - isn't shared. In a siloed org, the development team writes code to satisfy bug reports or feature requests, which come from a business analyst or product owner, who is the sole conduit to "the business". Why these things are needed, their relative priorities, or their ultimate impact, are not regarded as important concerns for the development team. tldr: software developers often can't measure the impact of their code, so they fall back on describing the technologies they use, which drives a counter-productive desire to employ "sexy" technologies.