[mikk0j]

Thanks. One specific example could be resource sharing. We use Github for code, but also for issue tracking (which brings with it discussion threads) so using Github properly even if not making code commits is valuable so you stay on top of issues and questions and can contribute. And in my case, I know I can make small fixes myself, so I want to have the infrastructure in place and know how to use it.

If you are working remotely, you want to be able to see the latest development version and run it locally, not just the latest alpha push. In the real gritty details, I just had to update Maven on my local machine and fix a Github conflict, and had to ask for help figuring out where the missing components were and how to fix the error messages. If someone has to take an hour helping me get this done, it is unnecessary overhead. I still almost broke things in vim though, but know what I have to learn.

More generally, a technical product understanding just helps in communication. If the tech lead makes the decision to refactor the code, which leads to delays affecting the business, it's good to know why.

[tdr]

> More generally, a technical product understanding just helps in communication. If the tech lead makes the decision to refactor the code, which leads to delays affecting the business, it's good to know why.

That's great! I'm interested mainly in these kind of benefits. Besides communication, how does it help your relationship with customers/team/partners?