I’ve run into this a few times in my career and I’ve found that teams usually purposely add “bureaucracy” to create boundaries between functions. For instance, in the early days of my first startup, I made all the “builds”, learned how to fix API bugs, even extending the external API wrapper, etc. I wasn’t a developer, rather I worked in support but we all agreed that it was everyone’s job to deliver value to customers and that we didn’t have time to worry about who fixes what.
Interestingly, as we got bigger, the walls went up. You could no longer just “fix” things, you had to get approval, then eventually a “sponsor” (I.e. another dev checking in your changes), finally, they asked you to just file a dev ticket and it would be prioritized (which was code for: this won’t get done any time soon).
I don’t know how to explain this, but it became a pattern at other companies as well.
