I don't, but it's probably because I've spent most of my career being the guy who did that part. I'm old (52), so while I did code initially in my career, I wa

I don't, but it's probably because I've spent most of my career being the guy who did that part. I'm old (52), so while I did code initially in my career, I was tempted away ($$) into roles where the fact that I'm also good at written and spoken communication was part of the remit. Being able to communicate with users AND understand how software is actually written turns out to be a remunerative skill. Like coding, though, it's not something just everyone can do well. Also like coding, you have to WANT to do it. If you're pushed into a role like this and you don't like it or don't want to do it, everyone will suffer -- you, the users, and the rest of the dev team. It's a recipe for sadness.