Programming today is stressful — way more stressful than I remember it in the 90s and early 2000s when I was just starting out.

Hacker News is a community-driven platform for sharing and discussing technology news, startups, and programming-related topics. Through user submissions and comments, Hacker News offers insights into emerging technology trends, industry developments, and entrepreneurial ventures. Readers can participate in discussions, share their insights, and stay informed about the latest advancements in technology and innovation.

Hacker News

Modern programming has become significantly more stressful compared to the 90s and early 2000s, particularly due to the adoption of sprint-based approaches like Scrum. Issues include the continuous nature of sprints, lack of autonomy, and insufficient preparation time before tasks. These factors contribute to a constant medium-level stress that is more harmful in the long run. Sustainable changes are needed to restore developer autonomy, professionalism, and reduce stress.

Why Scrum is Stressing You Out

3. Sprints Neglect Key Supporting Activities

Anyone that critizises Agile, doesn’t speak of an alternative or another way of doing things better…

Agile is good, it allows breaking big projects into smaller deliverable features and allows quick feedback during development. One large feature can span over multiple sprints
It only feels stressful when management is making it stressful. And with the same management, you feel stressed outside of agile.

I’m sorry to say that but the author doesn’t understand Scrum, sprints, or agile. But it’s probably not their fault either, because as they’ve already figured out themselves, it’s really just companies doing waterfall and abusing some concepts, or rather travesties thereof, of Scrum to make things worse.
When people blame “agile”, they are really blaming businesses pretending to be agile and continuing to do project development with micromanagement. We can’t even go post-agile because we’ve never been agile.

Completely agree. The while problem is the Business. They make promises based on very vague estimates from dev teams or they know the deadline, just get it to the dev team way too late.
Business needs to stop listening to so called Agile Experts, they are full of it. Promising the world and only breaking teams down by ceremonies and meetings.
Industry experts need to stand up and tell business how it should be done, for the sake of development teams. Else open source / leisure software takes over and becomes better than purchased / in house crap.