Do developers really get upset by constant growth experiments?

Quick question for frontend developers that work with growth teams:

How many of you really get upset by constant growth experiments and content changes? Would you prefer to focus on more challenging tasks, or is that actually ok for you?

I'm a growth person. A few years ago, I was that annoying person that kept asking my developer friend for constant changes on our website. Until he got tired of me and told me to learn how to code so I could do it myself.

Fast forward, we started croct.com to solve this problem, but I'm not sure how many of the devs despise this repetitive kind of task even today. We're still in beta, so we have few devs actually using it. And they absolutely love it. However we've already talked with many companies and teams who supposedly have this kind of problem. The point is that sometimes I don't feel this is an issue for them as it was for us.

Some of them use CMSs platforms to solve the problem of constant content changes. But then face the problem of integrating this with AB testing platforms so marketers can test their hypothesis. Then the design team gets pissed because marketers mess with the design system. Then the developer refactors the website to implement a headless CMS. Then the integration with testing platforms gets harder. Oh, did I tell you that the marketers have the idea to introduce some personalizations at some point? And that they also need data?

Apparently, some developers don't mind being in the middle of this mess. But at first, I was sure they would. Developers are driven by challenges, after all! And it doesn't seem challenging to me.

What are your thoughts on that?