When the tools you have don’t work, sometimes you need to take on the arduous task of building your own.
From there, it becomes a question of whether you’re going to share it with the team and others in its stable form or go the route of sharing how you built it with others (a la Github) or not share it with anyone at all.
The first option is pretty safe, people can’t see what your code looks like, so they use it, and thank you.
The second option is open to questions and interpretation – Why did you build it this way? Why use this language? Why structure your code that way?
More questions.
Third, you keep it all to yourself and bring it out to make your job go faster when needed.
I don’t know what the best answer is, I presume it depends on the scenario. I have never shared my code publicly on GIT, in a team, for sure. When consulting, I use the tools I built to save time to help accelerate projects.
I don’t think there is a perfect answer, just like there is no perfect tool that will do everything you need.
Sometimes you need to take a leap and build it yourself.
