I'm pretty much full stack - UX work is typically "post a prototype or sketch or plan, wait for feedback". I think this works better when one has strongly structured design protocols though.
I've worked through a lot of different fields getting to where I am now - for instance, warehouse inventory and paperwork handling raises the importance of accurate warehouse inventories (and they weren't low before) - but a lot of the paperwork could easily be done remotely these days. (sometimes I miss forklift driving - it was a lot less stressful than programming in many ways, although it required a much more immediate care and caution and physically higher risk)
I suspect that crosses a lot of other varieties of work - paperwork could be more offloaded or moved digital, while the key actions still require people, mostly.
And someone always has to maintain the infrastructure.
I've worked through a lot of different fields getting to where I am now - for instance, warehouse inventory and paperwork handling raises the importance of accurate warehouse inventories (and they weren't low before) - but a lot of the paperwork could easily be done remotely these days. (sometimes I miss forklift driving - it was a lot less stressful than programming in many ways, although it required a much more immediate care and caution and physically higher risk) I suspect that crosses a lot of other varieties of work - paperwork could be more offloaded or moved digital, while the key actions still require people, mostly. And someone always has to maintain the infrastructure.