Yes, `2-3 other people can work on it with you` would be splendid. But then you have to be on the same page with your colleagues on how to go on about doing things. You know how that goes, when good ideas are then made mandatory and all the team must follow suit. Then the original motivation is kinda lost in the background and then part of the team only does the moves because "someone told me to".
If you say, yes, `2-3 other people...`, let's get together and do this thing, approval or no approval, then we might be getting somewhere.
As an extreme example, if I'm using Emacs, and assume it offers some advantage in the project development velocity department (ignoring any reasons as to why, for the sake of the argument) but cannot convince the other team-members to use it, should I stop using it?
There's a difference between working in lockstep with every single other teammate and making your work available to other people. The former is sometimes the ideal, but the latter is always achievable.
I am maybe the only Emacs user in an eng org of 100 people. But my work is compatible with that of the VS Code and Vim users, of course.
If you say, yes, `2-3 other people...`, let's get together and do this thing, approval or no approval, then we might be getting somewhere.
As an extreme example, if I'm using Emacs, and assume it offers some advantage in the project development velocity department (ignoring any reasons as to why, for the sake of the argument) but cannot convince the other team-members to use it, should I stop using it?