I think the main issue most devs struggle with is not the changing requirements but that the timelines are not adjusted accordingly and have to be swallowed by

I think the main issue most devs struggle with is not the changing requirements but that the timelines are not adjusted accordingly and have to be swallowed by the dev with overtime. And in most cases when there is some adjustments it's not nearly enough to cover the actual costs. If that was somehow resolved I think the vast majority of devs would be fine with changing requirements. Problem is I don't think there is an easy way because most non-dev don't truly understand the costs involved. Fr example can u imagine telling a plumber no the bathroom is now going to be 30 feet to the left. The plumber says ok but that will cost u a week of work. How many people would say no, u have 1 day to do it and u will be held accountable for my estimate and not ur estimate because I don't trust u when u say a week. Now assume the walls are closed and it's only after u open them u learn there are other issues. Doesn't matter, one day. This is what most de s deal with. I assume ur not like this but this is how most devs have to work. It's frustrating. If u would be given the week then u would be fine, but instead ur told the timeline and/or cost. U may even be told no u can't use those tools they r too expensive, but u need to complete the task in the faster then even people who can use the tools. My whole point is it's often not the change requests that are the issue, it's what it entails, in that the schedule and costs are not adjusted fairly.