Typo Reviews & Product Details

It has plenty of tools that allow me to better understand my team performance, without going deep into many insights that could confuse me.

Before Typo, I had to crush data which took me a long time and deviated me from my management role. With Typo, there are only a few clicks and voilà, I have all the information I need from each of my Engineers, how the teams are behaving, what to do to fix/resolve slumps we might have, bugs within code and level up the team to be at our highest level possible.

Features like benchmarks within each insight help me visually to better understand where we are, Code Health also helps us understand much better the issues ( Bugs ) we have, the ones that aren't based on the best practices, and the ones we got wrong. Slack's integration allows me to watch when a PR or merge has been done without getting into Typo to find out about it. Review collected by and hosted on G2.com.

If you are a preseed/bootstrapped startup Typo's pricing ain't for you. Review collected by and hosted on G2.com.

In my role - the best part of Typo is it's easy to understand expression of Git Metrics. They are good enough that I'm able to directly use them with my leadership, and they're able to get a week-to-week pulse of how the engineering team is performing. Similarly, I review these metrics in a little more detail to help coach up some engineers, teams, and leaders.

For my team - they use it as team leads and individual contributors to get an understanding of how they work has been flowing. Admittedly, we could be doing better here, but Typo gives us all the data we need.

Rolling this out was pretty easy - mostly was three steps: (1) hooking up Github, (2) Configuring Typo to match our workflow, and (3) Meeting with their customer success team to go over any questions I had. I've had a few interactions with that team, and have been impressed with the speed of service and how knowledgable the team is. Review collected by and hosted on G2.com.

I haven't really found much that I dislike - there are some philosophical limitations that might catch some off-guard, like:

1. Metric calculation cannot be instantaneous on configuration change, as there is often a lot of history to recompute

2. Pure Git and Jira metrics are not going to measure team success directly. It's a great, necessary, tool to have under your belt - but you're never going to know if your having good "outcomes" from a tool like this

3. I've had relatively minor bugs that I've reported (but as with any great team, these were solved quickly) Review collected by and hosted on G2.com.

Typo helps my team have a clear view of what's going on, showing statistics and useful insights about the team focus and productivity.

It was very easy to integrate it in our day to day routine, making it easy to use daily or weekly Review collected by and hosted on G2.com.

Sometimes it takes a while to refresh the data (I know it's available for some profiles, but not for all) Review collected by and hosted on G2.com.

Literally took a minute to set up and worked seamlessly.

Instantly helped me inspect metrics about my engineering team that no other tool on the market managed to assemble and present.

I now consult my Typo dashboard everyday. Even the free features offer valuable insight.

Has a free tier for small teams. Review collected by and hosted on G2.com.

The code smell features don't behave too well with our team's type of development.

The core features are definitely built for bigger teams and SaaS/live-ops projects, which isn't always the case.

The pricing is pretty steep for a development analytics tool (higher cost per dev than our cloud SCM and wiki platforms combined) but the free tier is sufficient for me atm. Review collected by and hosted on G2.com.

Pull Request Summaries: The automatic summaries for pull requests are incredibly helpful, providing concise insights that speed up the review process and enhance team collaboration.

Code Review Protection: The typo code reviews effectively safeguard our codebase by identifying common issues before they escalate, ensuring a cleaner, more reliable code.

Static Code Analysis: The tooling for static code analysis is outstanding, allowing us to quickly detect code smells, vulnerabilities, and performance issues, which significantly improves our overall code quality. Review collected by and hosted on G2.com.

False Positives in Static Code Analysis: One notable downside is that many of the static code analysis issues reported are false positives. This can lead to unnecessary confusion and extra work for the team as we sift through the alerts to identify genuine concerns. Review collected by and hosted on G2.com.

Metrics integrated with github, they follow the best practices and deliver healthy and accurate metrics Review collected by and hosted on G2.com.

Nothing, I wish I had a tool integrated with terminal Review collected by and hosted on G2.com.

I love how quick I am able to ship my software without going back and forth to several other tools to get my code metrics and all. Review collected by and hosted on G2.com.

The code quality suggestion is a bit vague since its subjective. I hope the AI can improve on this. Review collected by and hosted on G2.com.

- Easy to setup (connects with Github)

- Easy to understand

- eMail / Slack alerts when someone commits without a review Review collected by and hosted on G2.com.

- There are still some issues with the frontend to be corrected Review collected by and hosted on G2.com.

With Typo, we are making much more informed decisions to drive performance improvements at the team as well as at the individual level. The best part of Typo is that it never makes my team members insecure and it produces the insights in the most healthy way possible. Another thing is their customization is out of par and their highly responsive support team Review collected by and hosted on G2.com.

I feel that Integration with tools like confluence could help us evaluate the workload at the individual dev level even better. Review collected by and hosted on G2.com.

Love that there's a single tool we can use to both analyse how sprints are running at the top level in terms of time to merge etc. and also to gather sentiment from the team.

Being able to send out weekly surveys to the team via slack and see differences across team gives us a good picture of any unexposed risks for those teams. Review collected by and hosted on G2.com.

Sometimes it can be a little difficult to drill down on some of the stats, more of a learning curve issue than an app issue. Review collected by and hosted on G2.com.