Pixel?tag=viewcontent&noscript=1

Static Object: A GitPrime Alternative for Technical Managers

1

Gitprime alternative for technical managers

Gp alt 1
1

Gitprime alternative for technical managers

Gitprime is designed for non-technical managers. It analyzes the team's commits without showing any of the code. By minimizing certain details, GitPrime makes the tool less intimidating for non-technical managers. The tradeoff is that you lose levels of information and control.  

Static Object is designed for technical managers. It analyzes the team's commits and shows how the code is being interpreted. Managers can see exactly how analysis happens and dig in to get as much detail as needed.

If you're a technical manager who is short on time but thrives on details, Static Object was made for you. We deliver technical insights, pronto.

2

Focus on a Single Reliable Metric

Gp alt 2
2

Focus on a Single Reliable Metric

Gitprime measures developers using four dimensions: commit volume, impact, code volume, and velocity. This offers a comprehensive look at developer performance, but also makes it more difficult to extrapolate unambiguous conclusions.

Static Object relies on a single, reliable metric, called Line Impact. For technical managers, the single metric approach confers numerous advantages:

  • Empirically match intuition to results. Line Impact provides a system that is flexible enough to be configured to match the judgement of your best software experts: your CTO, VP of Engineering, and other Engineering Managers. When these leaders see that Line Impact mirrors their own judgement, that confidence flows down to the developers themselves.
  • Clarity in conclusions. When running experiments like the "work from home" productivity test, more metrics add more ambiguity in what conclusion to draw. Using a single, reliable metric makes these comparisons trivial to interpret.
  • A reliable metric lets you analyze secondary dimensions. Spreading data across many metrics makes it impossible to facet data across secondary dimensions. For example, if you want to know who's the most prolific test writer, you can rank all developers' Line Impact on the secondary dimension of "test code." This isn't possible if you don't have a reliable metric to serve as your primary axis.

See also: "Why we focus on a single, reliable metric".

3

Cut code review time in half

Gp alt 3
3

Cut code review time in half

Since we were already building a rich and nuanced diff viewer for the sake of debugging our Single Reliable Metric, we decided to start offering it to our customers. In the future, people will say that this idea spread like wildfire.

If your job sometimes involves skimming code - or if you wish it did - or if you manage people who do - Static Object provides significant benefits beyond its use as a code metrics tool.

  • Reduce noise. Commit Groups slash the busywork required to read code. We bundle commits together based on your Standup meetings, by day, week, or whatever other interval you want to see what others are up to.
  • Commits presented concisely. Our original homepage tagline was "Cliffs Notes for Github" because our commit viewer is like a poem to Github's essay. When you can identify and discount moved code, whitespace, keywords, etc, commits get less complicated.
  • Encourage team buy-in. Static Object shows line-level detail on how Line Impact was calculated. When developers can understand the scoring, they trust it. Culture win.

Gitprime currently offers no code review, or ability to check out their Impact metric on a per-line basis. They haven't indicated it's in their roadmap.

Static Object reviews and summarizes the code, teasing out the fraction of the work that has a meaningful impact on the code base.
GeekWire Read the article
4

Precision code scoring with premium reliability

Gp alt 4
4

Precision code scoring with premium reliability

GitPrime and Static Object both spent years refining their scoring engines. While these engines differ, there is one key similarity.

Both draw sweeping conclusions from a small slice of committed code.

Both scoring engines rely on removing the noise from lines of code. Considering that roughly 95% of all committed lines are noise, it's important to precisely identify where the action is happening in a commit. Here's how we do it:

  • Discount language conventions. Keywords, blank lines, and other conventions make up almost 50% of code lines. The Static Object scoring engine is calibrated to ignore these lines in favor of others that made an impact.
  • Discount moved lines. Moved lines make up another 15% of changed code in an average repo, but don't add any value. Removing them from the equation results in more precise measurement.
  • Fine-tune scoring. A productive developer might write 500 lines per hour in CSS, but only 50 lines per hour in Python. Technical Managers can calibrate Line Impact per file type, so developers' Line Impact becomes standardized across disciplines.
5

Fair pricing for all teams

Gp alt 5
5

Fair pricing for all teams

Static Object's pricing reflects our commitment toward our small-to-medium business customers. Teams with fewer than 50 developers struggle to justify spending $1-5k per month on a development tool.

This is why our pricing is per contributor and access to tools is determined by plan, rather than team size. Your total remains much lower, while including top-tier customer service.

Contact us to see how Static Object can work for your team

Our sales team is available Monday - Friday, 9am - 5pm PT.

Request a 15 minute demo