Developer attribution: How it is calculated now on AI Code Monitor Tool
Video: https://youtu.be/FC7FweUYO2s
The AI Code Monitor tool is in Beta. Regarding Developer attribution, while the math is correct given a certain AI/ Not AI composition, the formula we picked first is one of several possible ways to think about developers’ code and GenAI.
For context, it’s very important to us that we help our clients blend, i.e. modify GenAI code to avoid security risk, code quality risk, diligence-at-exit risk (several major PE firms and strategists are now scanning for Blended usage).
So, if code was generated at Time1 by Developer1 and was not Blended initially, and then the code was modified at Time2 by Developer2, then we want the system to give credit for the code ultimately being Blended.
The current version of developer attribution works as follows:
Developer percentages refer to the amount of code in a moment in time. We get the whole codebase for a certain commit (the last of each day). Then we analyze chunks to set GenAI labels. For each line of each chunk, we attribute that line to the LAST developer that committed to them.
For example:
Let's say Developer1 pushes a function, which is PureAI. It has 30 lines. Developer1 gets 30 lines PureAI attributed to them.
Next day, Developer2 modifies 20 of those 30 lines. Now that entire chunk is labelled as Blended, but Developer2 has 20 lines Blended, and Developer1 has 10 lines Blended, even though Developer1 didn’t do anything on the next day.
