Library/Case studies/Sourcegraph
Sourcegraph
The code search company, which ran on a public handbook until 2024. Leo read it as it stood on 31 December 2021, and we followed its own history to the day it was archived.
Source: Sourcegraph's public handbook, Apache 2.0 licensed
ArticleWhat Leo saw at Sourcegraph, 1. The reason for late invoices, written down and left aloneIn 2021 Sourcegraph's handbook named why invoices ran late: 'missing contact or PO information'. Leo suggested carrying those details on the closed deal. When the handbook was archived in June 2024, the page was word for word the same.Finance · Sales · 3 min readArticleWhat Leo saw at Sourcegraph, 2. Every incident update, written five timesDuring an outage, Sourcegraph's incident messenger wrote each update for the status page and then again for four Slack channels, every 30 minutes. Leo suggested writing it once. Fifteen days later, the repeat posting was gone.Engineering · Customer support · 3 min readArticleWhat Leo saw at Sourcegraph, 3. The upgrade done by hand, again and againSourcegraph upgraded each hosted customer by hand, with a short outage every time. Leo laid out three ways forward: script it, keep each customer's settings apart, record the change first. By November 2022 all three were done.Customer support · Engineering · 3 min readArticleWhat Leo saw at Sourcegraph, 4. Five approvals in a row, and then a sixthA Sourcegraph job offer passed five approvers one after another, then was typed again for signature. Leo suggested approving in parallel. In 2023 Sourcegraph added a sixth approver. Some processes are slow on purpose, and Leo's card records that too.People · 2 min read
Nothing here says that yet. Try fewer words, or another word for it.