I have had the same thoughts. In my opinion, from the developer's perspective, there are two issues in the industry: 1. Conveyorization of development process.

I have had the same thoughts. In my opinion, from the developer's perspective, there are two issues in the industry: 1. Conveyorization of development process. Developers write code, that's it. Most what I have done for the past 6 years was do ticket-based work, constantly moving from project to project. Ironically, at the start of my carreer, I was responsible for an entire internal application (including designing new features, being on-call, and talking to end-users), so I grokked the entire setup and purpose. 2. Self-perpetuating push for constant change for the sake of change. Producer (e.g: tech corporation) releases an update to their product to improve some internal metric or make more money -> Consumer updates their product (or jumps on the hype for next big thing) -> Producer metrics go up -> Repeat. This keeps both Producer's and Consumer's developers employed while providing very marginal benefits. While this is a bit of a strawman, think of how many versions (and names!) Of .NET, or React, Angular, Vue or any other framework there has been over the last 10 years and whether each version improved much. Combine the two, and, as a developer, you don't know how what you're doing matters, nor why you're doing it at all.