"Code monkey" absolutely was and still is a thing. I was hired by Big Name Co originally to be staff but a reorg had me do typical senior position duties for around a year, and it was hell. Every decision was made over our heads, feedback was unwelcome because the feature had already gone through design and gotten layers of sign-offs from different areas of the org, etc. My sole purpose was to write code and review peer code. Staying there a full year was way too much.

Second point, requirements analysis is hard because:

* Different stakeholders have conflicting goals, sometimes mutually exclusive * Some stakeholders have ideas that are actively harmful to users, and you must flex political capital to nip it in the bud * Some stakeholders think they know what they want with a far greater degree of clarity than they actually do, and lack the time to sit down and suss out the nuances, because you're a side-show in the grander scheme of their own priorities.

Writing code is a heck of a lot easier than dealing with people at the edges.