I would. And honestly, I can. But I'm not the owner/maintainer of the full pipeline that gets The Product into the hands of the end user. I write the code. Some

I would. And honestly, I can. But I'm not the owner/maintainer of the full pipeline that gets The Product into the hands of the end user. I write the code. Someone else wants it stacked in a specific way that matches the production environment. But the path from my desk to that environment changes twice a quarter. And each change requires me to change something in the stack of tooling. Why? I honestly don't know. I suspect it's some kind of incompetence: employee turnover means less-experienced folks take over, and they don't know, or can't be bothered to learn, the previous guy's stack. Or the stack is chosen by the new Senior Middle Manager every time that position changes because he's not familiar with that last iteration of technobabble. Whatever the case, it's really because the company has become too unwieldy, hiring too many technology employees, and far too many business folk. You want me to stop "playing" with tools? Let me get deep knowledge on one set and stop getting new ones. Let me actually build something instead of forcing me to navigate the org structure every time "one inconsequential end user" wants to make a change to a feature.