Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Code Insights team page #2140

Merged
merged 15 commits into from
Jan 7, 2021
Prev Previous commit
Next Next commit
some updates to background
  • Loading branch information
Joelkw committed Dec 4, 2020
commit fc49d564d09431a11bff4a33499235edb136b093
15 changes: 15 additions & 0 deletions handbook/engineering/code-insights/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,11 +4,26 @@ The code insights team will be responsible for building and delivering [**code i

<img src="./screenshot.svg" alt="Screenshot of a code insights dashboard with graphs" />

## Background

Sourcegraph code insights can tell you things about your code at a high level. Here's a [demo](https://www.youtube.com/watch?v=XqeRb6Mc4Co) of a code insights prototype.

Only Sourcegraph can do this because we have universal code search. To know _anything_ about your code at a high level means you must know _everything_ about your code at a low level.

Code insights connects a lot of features that Sourcegraph already has and builds on top of them; we go beyond single-step code intelligence to help create the full cycle of analyzing, monitoring, and actionably changing a codebase.

Code insights is the first feature primarily built for non-search-based user personas.

Code insights will combine Sourcegraph-created metrics with other third-party data sources.

## Goals
jeanduplessis marked this conversation as resolved.
Show resolved Hide resolved

1. Expose the value of Sourcegraph's knowledge of your codebase to users at all levels of an organization.
1. Expose generalizable metrics that let our users measure and track their own goals, whether those are migrations, code smells, security needs, cross-collaboration, or other information about code.
1. Expose features that let our users build their own insights.
1. Expose features that let users explore insights by team, repo(s), or other sub-metrics.
1. Connect code insights to other Sourcegraph features – make a campaign to impact a metric or set up code monitoring to notify you about changes to an insight.
1. Add plug-and-play integrations to Sourcegraph code insights that let users easily integrate third-party data into their insights.

## We're hiring for this team!

Expand Down