Comment by kstrauser
> I’d rather have a tool that’s more customizable.
You think you would, until you do, and by then it's too late.
It's important to have good processes, but the point of all those processes is to help you make things more efficiently. Anything that leads to you spending extra time serving the process directly reduces the amount of real work you can do.
> the point of all those processes is to help you make things more efficiently
I think this viewpoint -- that these processes somehow could increase efficiency if only they were good -- has a lot to do with why engineers dislike systems like Jira, because they will never see the increased efficiency they are looking for.
Let me restate it in a way that I think is a little more nuanced:
The point of systems/processes is to lessen the amount of inefficiency in a group of people working together as that group a) gets larger, and b) experiences turnover.
Nothing's ever going to be as efficient as a single engineer that can build everything with all the details in their head at that very moment. But there's a limitation on size of problems you can solve doing that! So many people working on large problems hate their processes, because each individual person is doing less than if they were in a tiny, stable team, and they can feel this, even if the organization is making great progress.
(And then, at the largest sizes of organization, it's almost impossible to stop the org from crumbling from the weight of its own complexity. People do spend an awful lot of effort trying, though).