7 ms·
One obvious benefit of the internal tools at Google is that they're all integrated with each other. So any Googler can quickly: 1. Search another team's code
by codeapprove 4y ago
One obvious benefit of the internal tools at Google is that they're all integrated with each other. So any Googler can quickly:
1. Search another team's code
2. Quickly jump into a Cloud IDE to make a change
3. Build and test the code, because everyone uses one build system
4. Send that code off for review and have the review tool automatically select the right reviewers and run the right tests
For a simple change (let's say a typo fix) all of the above can happen in a single browser tab in under 5 minutes even if you've never been in that part of the code before.
----
While I'm here a shameless but relevant plug: if you're looking for a Google-like code review experience on GitHub check out https://codeapprove.com https://codeapprove.com
- zoomzoom 4y agoThe hardest part of this cycle for most teams are steps 2 & 3, getting a consistent development environment and build system across projects just does not happen. The loop is interrupted by the process of reviewing outdated docs, finding the people with the knowledge, and chatting with them to get a development environment running and helping with deploys to various QA/test environments before merging. At Coherence, we agree that code search and code review, along with automated code intelligence, are a huge step forward. Tools like sourcegraph, graphite, codeapprove are all solving important problems in the cycle. But we believe that the general approach of “building” vs “buying” development infrastructure for these key steps is holding teams back. Check us out at withcoherence.com if these sound like problems your team faces, too! (Disclosure, I’m a cofounder)