I think the “problem” is that ethical questions and nuanced thinking generally get in the way of “getting things done”. It seems that the software/startup/disruption community glorifies moving fast, shipping an MVP and then iterating on improving measurable metrics. None of these are conducive to dialectic and thinking carefully about consequences. Heck, the popularity of weak/dynamic typing and REPL-it-till-it-works shows that many programmers today aren’t willing to reason about effects even within their own code... leave alone societal consequences! Nothing wrong with that style of programming as such, but I think it’s a symptom of the ratio of thinking-to-doing that many find comfortable.

Software is unique in that it gives us the flexibility to fix bugs after shipping, unlike any other engineering field. Over the last few decades, we seem to have gotten increasingly carried away with emphasis on that feature. Also has to do with the incentive structure encouraged in SV.