github.com/sourcegraph/handbook · 901 pages scanned · 86 places where pages disagree · a sample of 10
A company handbook: security policy, pay, support rules and engineering runbooks.
Sourcegraph archived this handbook on GitHub in July 2024 and moved it to Notion; most quotes here are from the archive.
… In this case, an exception should be sought. Exceptions can only be signed off by the CTO.
Exceptions must have the signoff from the risk committee on an individual basis.
The process page and the policy page name different people who can sign off a risk exception.
Your laptop screen is set to lock after 10 Minutes of inactivity.
Change your laptop screen lock time from 5 Minutes (Sourcegraph standards) to 1 or 2 minutes
A security standard. The travel page states the standard as 5 minutes and links to the standards page, which says 10.
Backlog: An unordered set of work with no associated target or commitment dates.
Backlog: The ordered list of items to be tackled after items on the roadmap are complete
Engineering and product define the same word in opposite ways: unordered versus ordered.
… p0: All customer reported issues per our contractual p0 service level agreement definition here (even Cloud customers, though we don't have SLAs for them at this time).
se/p0: All customer reported issues per our contractual p1 service level agreement definition here.
One page defines priority 0 by the priority 1 agreement. A support engineer reading it commits to the wrong response time.
All HubSpot contacts are synced to Salesforce, usually within 15 minutes.
Most HubSpot contacts are synced to Salesforce, usually within 15 minutes.
A rep who believes every contact reaches Salesforce will never look for the ones a suppression list quietly blocks.
A: We re-run compensation ranges every 6-months, and our ranges move as the market moves.
We re-evaluate our compensation ranges every 12 months, in alignment with our Impact Review Process, to ensure our compensation remains up-to-date and market competitive.
The pay page says yearly; the manager guide says every six months.
Feedback and career growth conversations are ongoing, and not limited to our twice-yearly impact review cycles.
… our bi-annual impact reviews provide a great opportunity where in-depth, formal feedback can be provided both ways: teammate-to-manager, as well as manager-to-teammate …
While we expect our Managers to provide ongoing feedback with Teammates year-round in 1:1 meetings and informally, we also provide formal feedback via our annual "impact review" process, which takes place in February.
The review-cycle page and the manager guide disagree on how often reviews happen.
Running batch changes server-side is available both for self-hosted and Sourcegraph Cloud customers.
All Cloud instances have executors enabled by default, enabling the use of Server Side Batch Changes and Code Intel auto-indexing.
Today, running batch changes server-side is available on Cloud (formerly managed instances), provided that customers self-host executors.
A strategy page and a release note disagree on what Cloud customers have to run themselves.
… sts ---all --replicas=0 Then restart ONLY the pgsql and codeintel pods Start the pgsql: kubectl scale pgsql --replicas=1 Start the codeintel-db: kubectl scale codeintel-db --replicas=1 Copy the database files into the pods by running the following command from the root of the deploy-sourcegraph directory kubectl cp …
… replicas=0 Then restart ONLY the pgsql and codeintel pods Start the pgsql: kubectl scale deployment/pgsql --replicas=1 Start the codeintel-db: kubectl scale deployment/codeintel-db --replicas=1 Copy the database files into the pods by running the following command from the root of the deploy-sourcegraph directory kubectl cp …
Two copies of the same runbook; one command is missing the deployment prefix.
Contractors submit an invoice at the end of each month (including any reimbursable and recurring expenses) via email to our accounting team, ap@sourcegraph.comp .
All invoices should be sent via email to our accounting team, ap@sourcegraph.com All invoices will be paid through Airbase .
One character. Invoices sent to the first address don't arrive.
Your first scan produces the same kind of report for your spaces, and reading it changes nothing on your pages.