Chris noted that since they started using Gitential, he pays very close attention to coding hours, churn, and code volume. Thanks to the tool, he was able to rapidly identify major efficiency problems with a lot of code being rewritten causing high churn rates. Upon deeper examination, most of the code churn was concentrated in Android files written by a specific developer.
What caused the problem?
In a case like this, Chris needed to talk with the developer to find out what was going on. As it turned out, though the architect was one of the team’s best Unity developers, this was the first time he wrote anything in Android Studio. He didn’t think it would be a problem to learn a new tool while working on the project. Nevertheless, his lack of experience led to trying out different solutions with frequent rewrites, ultimately impacting product delivery.
Using Gitential insights he managed to find where he needed to look for the root cause and found a solution.