.png)
.svg)
.svg)
You're in great company.
We’re building a code visibility platform for development teams of all sizes, in companies at every stage—from startups to Fortune 500.
See the value and results from innovative teams using CodeSee that you can replicate across your team.
.svg)
Impactful resource savings using CodeSee for code review.
How Distribute Aid uses CodeSee to make the most out of each minute in code review.
Problem | For humanitarian aid organization, Distribute Aid, every minute in the development lifecycle matters. In fact, they’ve estimated each hour of their team members amounts to about $600 in humanitarian aid delivered. They were spending upward of 20 hours per month in code review—time that could otherwise be focused on more impactful development progress.
Solution | CodeSee made it possible for Distribute Aid to revamp its code review process. Maps allowed their devs to provide the code context needed for their global volunteer open source team to efficiently conduct reviews—they’ve entirely replaced their use of Github tooling with CodeSee. Now, they begin code review by looking at CodeSee as a team, using the visualized dependency relationships and Tours to provide context and guide review order.
Results | In Q1 2022, using CodeSee saved the Distribute Aid development team on average 10 hours per month in code review, amounting to an estimated $19,500 per quarter in aid delivered.
CodeSee made it possible for Distribute Aid to revamp its code review process. Maps allowed their devs to provide the code context needed for their global volunteer open source team to efficiently conduct reviews—they’ve entirely replaced their use of Github tooling with CodeSee. Now, they begin code review by looking at CodeSee as a team, using the visualized dependency relationships and Tours to provide context and guide review order.
In Q1 2022, using CodeSee saved the Distribute Aid development team on average 10 hours per month in code review, amounting to an estimated $19,500 per quarter in aid delivered.
Problem | For humanitarian aid organization, Distribute Aid, every minute in the development lifecycle matters. In fact, they’ve estimated each hour of their team members amounts to about $600 in humanitarian aid delivered. They were spending upward of 20 hours per month in code review—time that could otherwise be focused on more impactful development progress.
Solution | CodeSee made it possible for Distribute Aid to revamp its code review process. Maps allowed their devs to provide the code context needed for their global volunteer open source team to efficiently conduct reviews—they’ve entirely replaced their use of Github tooling with CodeSee. Now, they begin code review by looking at CodeSee as a team, using the visualized dependency relationships and Tours to provide context and guide review order.
Results | In Q1 2022, using CodeSee saved the Distribute Aid development team on average 10 hours per month in code review, amounting to an estimated $19,500 per quarter in aid delivered.
What customers are saying.
.svg)
Distribute Aid significantly cuts onboarding time with CodeSee.
How the humanitarian aid organization sees massive savings using CodeSee to onboard contributors.
Onboarding new developers to Distribute Aid open-source projects was requiring at least two four-hour pairing sessions to get folks up to speed. The sessions were challenging to schedule across a global team, and frequently left new volunteers feeling overloaded—an outcome that inspired project churn.
Distribute Aid integrated CodeSee into its onboarding workflow, including linking to CodeSee Maps in project README documentation. Prospective contributors were then able to asynchronously, easily explore the codebase, including project details placed in Labels and Notes—all before committing to a project. Not only did CodeSee help the Distribute Aid team preserve resources at the outset, but also in code review. Using Review Maps, project maintainers were able to quickly understand the proposed changes of incoming contributors.
In Q4 2021, Distribute Aid saw noteworthy improvement in its end-to-end onboarding experience. The team saved an estimated 72 hours in onboarding time, and received more contributions to its projects than ever before—9 pull requests from new contributors. Ultimately, the team was able to refocus effort on delivering additional project features and tackle operational challenges—a set of feats resulting in an estimated $43,200 in aid delivered!
Problem | Onboarding new developers to Distribute Aid open-source projects was requiring at least two four-hour pairing sessions to get folks up to speed. The sessions were challenging to schedule across a global team, and frequently left new volunteers feeling overloaded—an outcome that inspired project churn.
Solution | Distribute Aid integrated CodeSee into its onboarding workflow, including linking to CodeSee Maps in project README documentation. Prospective contributors were then able to asynchronously, easily explore the codebase, including project details placed in Labels and Notes—all before committing to a project. Not only did CodeSee help the Distribute Aid team preserve resources at the outset, but also in code review. Using Review Maps, project maintainers were able to quickly understand the proposed changes of incoming contributors.
Results | In Q4 2021, Distribute Aid saw noteworthy improvement in its end-to-end onboarding experience. The team saved an estimated 72 hours in onboarding time, and received more contributions to its projects than ever before—9 pull requests from new contributors. Ultimately, the team was able to refocus effort on delivering additional project features and tackle operational challenges—a set of feats resulting in an estimated $43,200 in aid delivered!
.jpg)
Understand your codebase.
Get started for freeLet's connect!
Connect with us in our digital channels + sign up to receive updates on Maps.
Plus, consider booking a 15-minute personal pairing session with a CodeSee engineer to explore your Maps needs, or join one of our 30-minute Office Hours sessions.
