What is Knowledge Sharing?

Knowledge Sharing has a high significance in the quality of your product. This section is dedicated to maintaining the quality of your product and generally shows if and where the team needs training or needs to be on equal footing with their coding knowledge.

Single Author Files

What is Single Author Files?

The Single Author Files metric is the number of files only contributed to by only one author.

What does Single Author Files do?

This metric can indicate a large knowledge gap in the team. The number should be kept to a minimum such that the knowledge within the codebase is shared around adequately. If it isn’t there will be a large, non-understandable chunk of code for a majority of the team.

Why use Single Author Files?

It can help catch problem before they actually occur and in some cases stop critical misunderstandings in case the original author leaves the team. The problems that can arise should knowledge siloing take place is: maintainability, accountability, efficiency, bottlenecks, and human resource risk.

Percentage of Single Author Files

What is Percentage of Single Author Files?

The Percentage of Single Author Files metric is the percentage of files only contributed to by only one author.

What does Percentage of Single Author Files do?

This metric can indicate a large knowledge gap in the team. The number should be kept to a minimum such that the knowledge within the codebase is shared around adequately. If it isn’t there will be a large, non-understandable chunk of code for a majority of the team.

Why use Percentage of Single Author Files?

It is a much more quantitative view of Single Author Files and should be used in tandem with it to find any knowledge gaps.


Single Author File Distribution

What is Single Author File Distribution?

The Single Author File Distribution metric is a visual view of single/double author files that were changed more than 10 times

What does Single Author File Distribution do?

This metric can indicate a large knowledge gap in the team. Reasons for rapid file editing could be:

  • The core / important part of the project

  • Complex so it is hard to get right

Why use Single Author File Distribution?

It is a visual view of Single Author Files and should be used in tandem with it to find any knowledge gaps. These rapidly-edited files are more risky if only one or two contributors are familiar with it. Drill-down on files to find out the who's and why's.

Language Worked on By Contributors

What is Language Worked on By Contributors?

This graph gives a view of how much code is written in different languages by how many contributors per language.

What does Language Worked on By Contributors do?

It helps you find if there is a siloing of knowledge within the codebase and by how many people. A large language chunk with very few contributors could signal knowledge siloing.

Why use Language Worked on By Contributors?

Language Worked on By Contributors should be used in tandem with Single Author Files to find out which language(s) the team most needs training in such that the knowledge gap can be lessened.

Did this answer your question?