GitClear - Data-driven insight for developer impact and code review

Hi Product Hunt, Kevin from Static Object here. @williambharding created Static Object to lessen the pain when our first product, Bonanza.com, started scaling up its development team. By the time we hit 10 developers, it had become prohibitively time-consuming for our CTO and Engineering Manager to get answers to what seemed like they should be simple questions: - Who's working on what across our 20 different repos? Is anyone stuck? - How does new hire Bob's code output from his first three months compare to the first three months of one of our senior developers, like Alice? Do we really need to wait 6 months before we can make informed statements about Bob's performance? - How can we avoid recency bias during Alice’s performance review, i.e., what was Alice working on 9 months ago and how did that go? Over the past months, has Alice been most productive writing code in front-end, back-end, tests, the mobile app, or something else? - Does our weekly "work from home" day impact productivity? By how much? What effect do our meetings have on engineering output in general? - What Jira issues has each developer worked on since our last Standup Meeting? What progress have they made on those? From a pure code review standpoint, GitHub could suffice, but reading commits scales poorly across multiple repos. Not to mention how common it is that the code within a Github commit will have been changed or deleted by the time it's reviewed. For productivity-based questions, our options were far worse. All of the prior art was based on commit or code line counting -- both effectively useless for gauging the impact made by a developer. Online discussions of code metrics labeled the challenge essentially "unsolvable" (one representative example). But we were hopeful. If a Lead Developer can understand their developers' strengths and opportunities by reading commits, then why couldn't we teach a learning algorithm to do the same and let the Lead Developer spend their time coding instead? All of this brings us to present: a tool that can map how code changes over time, intelligently group commits of similar purpose, and help Lead Developers, Project Managers, and CTOs get unprecedented insight into the life of their developers. We are excited to be on Product Hunt and would love your feedback. We will be here all day to answer any questions. Please check out the sandbox we have create just for PH users, and let us know what you think! (Sandbox is currently only available on desktop. Full mobile support coming soon)

Developer and team reports are a great way of measuring how your team is holding up

Pros:

Great way to analyze developer performance and workload

Cons:

PR's need a bit of work

Looking forward to seeing new features and tools!

Pros:

Excellent way to monitor project data!

Cons:

Getting developers buy-in on measuring output can be a

challenge.

Excited to see what else can be done in this space, and SO seems to be leading the pack. Has helped improve my personal productivity as a dev.

Pros:

Tackles a hard topic - visualizing developer performance - and does it well. The graphs pop out well and all of the data seems relevant.

Cons:

Supports JIRA integration, but tying commits to issues is limited. It can only be done via a tag in the commit message right now.

Interesting approach to analyze activity within code bases (e.g. green field development vs maintenance etc etc).