profile
viewpoint
Nick Snyder nicksnyder @sourcegraph San Francisco, CA

linkedin/LayoutKit 3085

LayoutKit is a fast view layout library for iOS, macOS, and tvOS.

nicksnyder/go-i18n 1391

Translate your Go program into multiple languages.

nicksnyder/ios-cell-layout 12

How to use autolayout for dynamically sized UITableViewCells

nicksnyder/basen 8

A base62 and base58 encoding library for Go

nicksnyder/go-securetoken 7

The securetoken package implements web-safe secure tokens in Go.

nicksnyder/activity 1

Activity is a command line tool that summarizes a person's activity from various services.

nicksnyder/docs 1

My personal style guide

nicksnyder/IBDesignableExamples 1

Example usage of @IBDesignable and @IBInspectable

nicksnyder/AndroidNativeVsWebView 0

Compare performance of native rendering vs WebView rendering

pull request commentsourcegraph/sourcegraph

Add CodeQL Analysis workflow

Splitting the analysis by language seems like a smart thing to do regardless, but 8 minutes would still slow our CI on PRs (our current PR builds take 5 minutes) so I would be hesitant to enable it on PRs.

Our current master builds (which do things like build and push docker images) take 11 minutes, so we could consider doing these checks per commit there.

jhutchings1

comment created time in 9 hours

pull request commentsourcegraph/about

Add #customer-updates to channels with non-standard retention

We don't want to try to store this information outside of Slack moving forward?

dadlerj

comment created time in a day

push eventsourcegraph/about

Nick Snyder

commit sha 4d78ce0ff5356c2bb4e8076147d4f68f5d644ce7

Update tracking_issues.md

view details

push time in a day

push eventsourcegraph/about

Nick Snyder

commit sha 08b2ea8b15e0109515c3dfe35ca4ed32ff7d599a

Update tracking_issues.md

view details

push time in a day

delete branch sourcegraph/about

delete branch : schedulingpreferences

delete time in a day

push eventsourcegraph/about

Nick Snyder

commit sha 8b5e00922f0c90945ffa9b6ad0d4b3b09dc1123f

Schedule interviews according to candidate preferences (#1161)

view details

push time in a day

PR merged sourcegraph/about

Reviewers
Schedule interviews according to candidate preferences

There is no one-size-fits-all solution. We should ask candidates what they want and then try to accommodate the best we can.

+4 -4

0 comment

1 changed file

nicksnyder

pr closed time in a day

push eventsourcegraph/about

Nick Snyder

commit sha 9331d7e2e08cb6e09c9c45ea0794492471317c88

Update handbook/people-ops/interview_process.md

view details

push time in 2 days

Pull request review commentsourcegraph/about

Schedule interviews according to candidate preferences

 We want to mimimize the bias in our hiring process, so we will try to avoid sche  ## Scheduling -We are flexible when it comes to scheduling interviews because we are all-remote and we don't need to schedule all interviews back-to-back (unlike typical onsite interviews at other companies).+We are flexible when it comes to scheduling interviews because we are all-remote and we don't need to schedule all interviews back-to-back (unlike typical onsite interviews at other companies). Some candiates like spreading interviews out over multiple days and others prefer to batch them as much as possible to get it over with. *Ask the candidate what their preferences are and then try to accommodate those preferences as much as possible (given interviewer availability)*.

Yeah not a binary choice. I tweaked your wording a bit.

We are flexible when it comes to scheduling interviews because we are all-remote and we don't need to schedule all interviews back-to-back (unlike typical onsite interviews at other companies). Some candidates like spreading interviews out (e.g., across multiple days and/or having breaks between interviews on the same day) and others prefer to batch them as much as possible to get it over with. *Ask the candidate what their ideal interview schedule looks like and then try to accommodate those preferences as much as possible (given interviewer availability)*.
nicksnyder

comment created time in 2 days

push eventsourcegraph/about

Nick Snyder

commit sha d626a11315df9fdde17bc0a9980c3e1b3b813a15

Update handbook/people-ops/interview_process.md Co-authored-by: Erik Seliger <erikseliger@me.com>

view details

push time in 2 days

PR opened sourcegraph/about

Reviewers
Schedule interviews according to candidate preferences

There is no one-size-fits-all solution. We should ask candidates what they want and then try to accommodate the best we can.

+4 -4

0 comment

1 changed file

pr created time in 2 days

create barnchsourcegraph/about

branch : schedulingpreferences

created branch time in 2 days

delete branch sourcegraph/about

delete branch : codeintelteam

delete time in 2 days

push eventsourcegraph/about

Nick Snyder

commit sha 0d107403735cf6c267d21ffe8034b993da13640b

Update code intel team (#1160)

view details

push time in 2 days

PR merged sourcegraph/about

Update code intel team
+4 -4

0 comment

1 changed file

nicksnyder

pr closed time in 2 days

push eventsourcegraph/about

Nick Snyder

commit sha 6282a98298a2e7ca8fed64f1f2814a1325e2c34e

Update index.md

view details

push time in 2 days

PR opened sourcegraph/about

Update code intel team
+4 -4

0 comment

1 changed file

pr created time in 2 days

create barnchsourcegraph/about

branch : codeintelteam

created branch time in 2 days

Pull request review commentsourcegraph/about

Add "Making an offer" section to People Ops docs

 Here are some other questions that candidates have asked (e.g., in the [CEO inte 1. What is the current runway and the monthly burn rate? 1. How much cash does the company have in the bank? 1. Other [questions about Sourcegraph's internal financial metrics](../ceo/index.md#questions-about-sourcegraph).++## Making an offer++Once the decision is made to [extend an offer](interview_process.md#outcome) to a candidate, the hiring manager and a representative from the People Ops team will schedule a call to walk through a summary of the offer. This summary will include an overview of cash compensation (including any commission or bonus plans), benefits, and any equity-based compensation (including a simple calculator for potential future values).++With the candidate's approval, Sourcegraph will then conduct three reference check interviews with former peers and at least one former manager. If these all come back positive, the Sourcegraph legal team will send the official DocuSign with the appropriate contracting or employment agreement(s) for the candidate's role, status, and location. Templates for employees and contractors can be found in the shared [HR/Employees/Contractors Dropbox folder](https://www.dropbox.com/home/Legal/HR%3AEmployees%3AContractors).

I am worried that If these all come back positive implies that one bad reference will necessarily tank your offer.

With the candidate's approval, Sourcegraph will then conduct three reference check interviews with former peers and at least one former manager. If we are happy with the results, the Sourcegraph legal team will send the official DocuSign with the appropriate contracting or employment agreement(s) for the candidate's role, status, and location. Templates for employees and contractors can be found in the shared [HR/Employees/Contractors Dropbox folder](https://www.dropbox.com/home/Legal/HR%3AEmployees%3AContractors).
dadlerj

comment created time in 2 days

issue commentsourcegraph/sourcegraph

Sourcegraph.com behaves like customer instances for a subset of repositories

@beyang is working on this: https://sourcegraph.slack.com/archives/CHPC7UX16/p1593446317093200

nicksnyder

comment created time in 2 days

Pull request review commentsourcegraph/about

distribution roadmap

  The distribution team is responsible for making Sourcegraph easy to deploy, scale, monitor, and debug. We solve challenging problems that our customers face when they deploy and scale Sourcegraph on-premise in a variety of environments, and that we face when we deploy and scale [Sourcegraph.com](https://sourcegraph.com/search) (the largest Sourcegraph installation in the world). -## Team API--- Slack: #distributioneers channel or @distribution-- File issues: [team/distribution](https://github.com/sourcegraph/sourcegraph/issues/new?labels=team/distribution) label-- What we're currently working on: [tracking issue](https://github.com/sourcegraph/sourcegraph/issues?q=is%3Aissue+is%3Aopen+label%3Ateam%2Fdistribution+label%3Atracking+distribution), [roadmap](https://docs.google.com/document/d/1cBsE9801DcBF9chZyMnxRdolqM_1c2pPyGQz15QAvYI/edit#heading=h.mi8zg2ql2uc6)--## Ownership areas--The following is a breakdown of the areas of Sourcegraph that the Distribution team owns. It aims to be 100% comprehensive, but the owners are merely aspirational goal posts, not mandates. At the end of the day, whoever has most context will own the area.--Distribution team members may also be involved in other areas of Sourcegraph not mentioned here (i.e., you're not restricted just to the distribution team or working on just the areas of ownership assigned below.)--- **Infrastructure**-    - Sourcegraph.com-    - Dogfood instances (k8s.sgdev.org, sourcegraph.sgdev.org)-    - 3rd-party services (ghe.sgdev.org)-    - Buildkite, CI pipeline / infrastructure.-    - **Primary owners:** @geoffrey, @dave-    - **Related code**: [infrastructure repository](https://github.com/sourcegraph/infrastructure), [CI pipeline code](https://sourcegraph.com/search?q=repo%3A%5Egithub%5C.com%2Fsourcegraph%2Fsourcegraph%24+file%3Abuild.sh%7C%2Fci%2F+count%3A1000&patternType=literal)-- **Release pipeline**-    - End-to-end release process infrastructure-    - Creating monthly releases-    - Testing environments when applicable-    - Releasing security updates when asked to-    - **Primary owners:** @uwe-    - **Related code**: [release captain experience](https://about.sourcegraph.com/handbook/engineering/releases#release-captain), [release tooling](https://sourcegraph.com/github.com/sourcegraph/sourcegraph/-/tree/dev/release)-- **Deployment**-    - **Kubernetes cluster installation & upgrade experience**-        - Kubernetes YAML & associated tooling-        - Cloud-specific setup docs (AWS/Google Cloud)-        - Deployment setup & upgrade docs-        - **Primary owners:** @uwe, @geoffrey-        - **Related code**: [deploy-sourcegraph repository](https://github.com/sourcegraph/deploy-sourcegraph), [cluster installation docs](https://sourcegraph.com/github.com/sourcegraph/sourcegraph/-/blob/doc/admin/install/cluster.md)-    - **Docker Compose & pure-docker installation & upgrade experience**-        - Docker-compose YAML & associated tooling-        - Pure-docker shell scripts & upgrade docs-        - Cloud-specific setup docs (AWS/Google Cloud)-        - Deployment setup & upgrade docs-        - **Primary owners**: @stephen, @geoffrey-        - **Related code**: [deploy-sourcegraph-docker repository](https://github.com/sourcegraph/deploy-sourcegraph-docker), [docker-compose installation docs](https://sourcegraph.com/github.com/sourcegraph/sourcegraph/-/tree/doc/admin/install/docker-compose), [docker-compose upgrade docs](https://sourcegraph.com/github.com/sourcegraph/sourcegraph/-/blob/doc/admin/updates/docker_compose.md) [pure-docker upgrade docs](https://sourcegraph.com/github.com/sourcegraph/sourcegraph/-/blob/doc/admin/updates/pure_docker.md).-    - **Single-container installation & upgrade experience**-        - Primarily in maintenance mode-        - Pushing admins to upgrade to Docker Compose-        - Communicating the limitations of single-container deployments-        - **Primary owners**: @stephen-        - **Related code**: [cmd/server in main repo](https://sourcegraph.com/search?q=repo:%5Egithub%5C.com/sourcegraph/sourcegraph%24+file:cmd/server/&patternType=regexp)-    - **Scalability**-        - Documenting when to upgrade from one deploy type to another-        - Resource estimation for new deployments-        - Scaling advice for existing deployments-        - **Primary owners**: @stephen-        - **Related code**: [resource estimator docs](https://docs.sourcegraph.com/admin/install/resource_estimator), [resource estimator repository](https://github.com/sourcegraph/resource-estimator), [Kubernetes scaling docs](https://docs.sourcegraph.com/admin/install/kubernetes/scale)-- **Observability: Monitoring** ("site admins should easily know the health of Sourcegraph")-    - Monitoring & alerting infrastructure-    - Educating site admins about how to monitor Sourcegraph-    - Working with & ensuring engineering @ Sourcegraph adds needed monitoring-    - **Primary owners**: @stephen, @uwe-    - **Related code**: [monitoring generator (dashboards/alerts)](https://sourcegraph.com/github.com/sourcegraph/sourcegraph/-/tree/monitoring), [Grafana docker image](https://sourcegraph.com/github.com/sourcegraph/sourcegraph/-/tree/docker-images/grafana), [Prometheus docker image](https://sourcegraph.com/github.com/sourcegraph/sourcegraph/-/tree/docker-images/prometheus)-- **Observability: Debugging** ("site admins should be able to collect the information needed to debug issues easily")-    - Logging & Tracing infrastructure-    - Working with & ensuring engineering @ Sourcegraph adds needed logging/tracing to debug issues-    - Making the debugging process for common problems seamless and straightforward-    - Making reporting issues with all needed information easy-    - Ensuring logs/tracing are not overly verbose, identify most useful information for solving problems-    - **Primary owners**: @stephen-    - **Related code**: [Jaeger Docker images and code](https://sourcegraph.com/search?q=repo:%5Egithub%5C.com/sourcegraph/sourcegraph%24+file:jaeger&patternType=literal), [opentracing code (broadly)](https://sourcegraph.com/search?q=repo:%5Egithub%5C.com/sourcegraph/sourcegraph%24+opentracing&patternType=literal), Jaeger [k8s](https://sourcegraph.com/search?q=repo:%5Egithub%5C.com/sourcegraph/deploy-sourcegraph%24+jaeger&patternType=literal), [docker-compose/pure-docker](https://sourcegraph.com/search?q=repo:%5Egithub%5C.com/sourcegraph/deploy-sourcegraph-docker%24+jaeger&patternType=literal), and [single-container](https://sourcegraph.com/search?q=repo:%5Egithub%5C.com/sourcegraph/sourcegraph%24+file:cmd/server+jaeger&patternType=literal) deployments & [associated docs](https://sourcegraph.com/search?q=repo:%5Egithub%5C.com/sourcegraph/sourcegraph%24+file:doc/admin/observability+jaeger%7Ctracing&patternType=regexp)--## Tech stack--Go, Docker, Kubernetes--## Details--* [Recurring processes](./recurring_processes.md)-* [Internal infrastructure](./internal_infrastructure.md)-* [Tools](./tools/index.md)-* Tutorials-  * [Observability developer guide](observability/index.md)-  * [How to set up a separate website maintained by Sourcegraph](separate_website.md)-  * [How to replay a metrics dump from a customer](use_metrics_dump.md)-  * [How to simulate k8s admin security restrictions](k8s_admin_custom_policy.md)-  * [How to test the Gitlab native integration locally](gitlab_native_local.md)-  * [How to make updates to global settings and configuration on sourcegraph.com](update_sourcegraph_website.md)+## Where to find us
## How to contact us
slimsag

comment created time in 6 days

Pull request review commentsourcegraph/about

distribution: Update meetings format

 As with everyone at Sourcegraph, we join the [weekly company meeting](https://ab  ### Weekly Distribution team sync -Mon @ 2pm PST we hold an [internal+Mon @ 11am PST we hold an [internal team sync](https://docs.google.com/document/d/1otP6F8qfm2yNOW1hjTszkkuiYF1MGp31s5ATeA76ij4/edit) via Zoom. It usually does not involve product managers or higher ups. The goal is to:
team sync](https://docs.google.com/document/d/1otP6F8qfm2yNOW1hjTszkkuiYF1MGp31s5ATeA76ij4/edit) via Zoom. The goal is to:

Please also delete the "### Distribution management sync" section since that meeting doesn't exist anymore.

pecigonzalo

comment created time in 6 days

push eventsourcegraph/about

Nick Snyder

commit sha d0c983fdfbe1705b2049bca1739c7fad4fbdf45e

Clarify manager progress updates (#1130)

view details

push time in 7 days

delete branch sourcegraph/about

delete branch : managerupdateclarifications

delete time in 7 days

push eventsourcegraph/about

Nick Snyder

commit sha 47910a87e3d6a49bb1648e7044b07e27224a518e

improvements

view details

push time in 7 days

push eventsourcegraph/about

Nick Snyder

commit sha 1467b47c8d3aa4e965beb1050c2bf78c36bdd916

Pre-read debrief feedback (#1146)

view details

push time in 7 days

delete branch sourcegraph/about

delete branch : preread-debrief-feedback

delete time in 7 days

PR merged sourcegraph/about

Reviewers
Pre-read debrief feedback

@ryanslade Suggested in a debrief today that everyone pre-reads all feedback before the debrief to save the group time. This PR updates our docs to indicate that is indeed what we want.

+1 -1

0 comment

1 changed file

nicksnyder

pr closed time in 7 days

push eventsourcegraph/about

Nick Snyder

commit sha 4ca58590ba3108c9c1bd2846a20107343ef3262e

Progress update for VP Eng okrs (#1147)

view details

push time in 7 days

delete branch sourcegraph/about

delete branch : vpengokrs

delete time in 7 days

PR merged sourcegraph/about

Reviewers
Progress update for VP Eng okrs

Don't have an update for other KR because not sure how to measure it yet.

Neither of the KRs under Raise the quality bar of our application and product turned out to be very good.

+3 -3

0 comment

1 changed file

nicksnyder

pr closed time in 7 days

push eventsourcegraph/about

Nick Snyder

commit sha 40ae96ce842fbb7bcefebc040f5f218a54667c34

hiring okrs

view details

push time in 7 days

push eventsourcegraph/about

Nick Snyder

commit sha 62e77f86e1910150bb3ea77a5f05a1d439cd082c

How to transfer teams (#1129)

view details

push time in 7 days

delete branch sourcegraph/about

delete branch : switching-teams

delete time in 7 days

PR merged sourcegraph/about

Reviewers
How to transfer teams

Add some brief docs that if you want to switch teams then just talk to your manager.

Adding these docs because a candidate asked: https://sourcegraph.slack.com/archives/C168VP0FM/p1593451725340400

+4 -0

0 comment

1 changed file

nicksnyder

pr closed time in 7 days

PR opened sourcegraph/about

Reviewers
Progress update for VP Eng okrs

Don't have an update for other KR because not sure how to measure it yet.

Neither of these KRs turned out to be very good.

+1 -1

0 comment

1 changed file

pr created time in 7 days

push eventsourcegraph/about

Nick Snyder

commit sha efe31b528e7d3f2fc4954f2d4c6de1b7ea17b998

Add places where we post jobs (#1052)

view details

Eric Fritz

commit sha 8e6f51e0c5161b6c2d2ae9f0a062612e9e1f0be2

Update code intel team tech stack (#1049)

view details

Eric Brody-Moore

commit sha d25751364657b72d55e9ffc0558ac23a6652f705

Add bizops commitments for updating financial metrics (#1054)

view details

aileenrose

commit sha 0b975fd920ca52a6c4633879184accfa987860d2

Add logo (#1056)

view details

aileenrose

commit sha e1a4c355f9e3766647cf9c906592a309f02f312e

Additional changes to code-xy pages to improve readability (#1055) * Code page changes - Add GitLab video to code review - Clean up headers of CTAs to allow users to read through page - Clean up spacing in Jumbotron * Update website/src/pages/product/code-review.tsx Co-authored-by: adam <41576481+adaaaam@users.noreply.github.com> * Update website/src/pages/product/code-review.tsx Co-authored-by: adam <41576481+adaaaam@users.noreply.github.com> * Move 2nd demo video below integrations Co-authored-by: adam <41576481+adaaaam@users.noreply.github.com>

view details

Beyang Liu

commit sha f83f06b6ced3e96e72138ff00105067c0321fb32

podcast: publish david cramer

view details

Quinn Slack

commit sha 39cd39c771ed8a25650ea89fc69addae92b86d98

update how I decide what a company meeting's focus is

view details

adamfrankl2015

commit sha 1eeeae852f373380fa82c2a87aac7c40bcee8ff1

Update 2020_q2.md

view details

adamfrankl2015

commit sha 7ebc0d84213de3be173df4e8ce642b7dbea40bed

Update 2020_q2.md

view details

Tomás Senart

commit sha 0aca4203153ba77f8529e9891a244c46e6cab789

team: Welcome to the Cloud, Dax (#1057) This PR updates the handbook team pages to welcome Dax on the Cloud team. He'll be helping with all things infrastructure in the context of the evolving [RFC 151 roadmap](https://docs.google.com/document/d/1qSSo83MJNcNbJhQOhDyHsGBCYPjyr7uhVQKGfZ8Vxfg/edit#heading=h.az00lc90wa5j), starting with [RFC 174 - HA Postgres](https://docs.google.com/document/d/1zNy-9QTAS4-i4C-ooFsfSwLf-kdnIJlTE8-uyub6-Ik).

view details

Pooja Jain

commit sha dccb1844642aff96ec4de5b10d088ffe0b4617a1

Add intro to Team Page (#1058) Co-authored-by: Pooja Jain <pooja@sourcegraph.com>

view details

Nick Snyder

commit sha 40cedf8e78394c49ab10d09af83e494bb9241960

Add headcount for backend engineer hiring (#968)

view details

Nick Snyder

commit sha dddec41f08f1e7db89d5ae93b14a2e756e9f765b

Remove references to "whitelist" (#1065)

view details

Quinn Slack

commit sha 7b9578b4fa34d72e7ec5003680fbca705320af20

desktop computers are ok (#1044)

view details

Robert Lin

commit sha 1211df2a3ca41bfc9ef2d6a829abb909484416a3

distribution: add upgrading grafana docs (#1053)

view details

aileenrose

commit sha 1162306c16ca2ca768975a84f263223f79eaa05b

Minor copy edits on all code pages for better clarification (#1062) * Minor copy edits on all code pages to emphasize Sourcegraph * Update website/src/pages/product/code-change-management.tsx Co-authored-by: adam <41576481+adaaaam@users.noreply.github.com> Co-authored-by: adam <41576481+adaaaam@users.noreply.github.com>

view details

aileenrose

commit sha f36c9356557f10f6e09750883eec49394fdfc132

Update customer logos and news (#1063) * - Add Button - Add Security Blvd news with updated logo * Replace with sharper logos

view details

Beyang Liu

commit sha c1547a9710220d83758a88c8f189dcbc058ae007

podcast: episode 2: ryan djurovich don't preload audio on page load

view details

Nick Snyder

commit sha 5cdd3f0e1374c7fbb91d03582add8097e75fba34

Delete PricingTable.tsx (#1064)

view details

Robert Lin

commit sha 5a682ad0ab7c71cf24766246911e15081d820ff6

add third-party license documentation (#1067)

view details

push time in 7 days

create barnchsourcegraph/about

branch : vpengokrs

created branch time in 7 days

push eventsourcegraph/about

Nick Snyder

commit sha 7cdf8d39c50bf983cd5212dc6a0f5a79a291389c

Update interview_process.md

view details

push time in 7 days

PR opened sourcegraph/about

Reviewers
Pre-read debrief feedback

@ryanslade Suggested in a debrief today that everyone pre-reads all feedback before the debrief to save the group time. This PR updates our docs to indicate that is indeed what we want.

+1 -1

0 comment

1 changed file

pr created time in 7 days

create barnchsourcegraph/about

branch : preread-debrief-feedback

created branch time in 7 days

push eventsourcegraph/about

Nick Snyder

commit sha 80ac9ef77b5cae9f0afe281b8f68282b2082c6ee

Innovation time (#1135)

view details

push time in 7 days

delete branch sourcegraph/about

delete branch : innovationtime

delete time in 7 days

PR merged sourcegraph/about

Reviewers
Innovation time

@unknwon started a thread in slack: https://sourcegraph.slack.com/archives/CHPC7UX16/p1593480102102700

Instead of responding there, I decided to propose an update to our handbook.

+11 -0

0 comment

1 changed file

nicksnyder

pr closed time in 7 days

push eventsourcegraph/about

Nick Snyder

commit sha dad71047fcfc75ca3b3d2ae3ccb9668fa9ae90f5

Fix links

view details

push time in 7 days

Pull request review commentsourcegraph/about

Innovation time

 If there is a dispute about ownership, then perform a [clean escalation](../comm - [VP Engineering](roles.md#vp-engineering) - [Software Engineer](roles.md#software-engineer) +## Innovation time++We love it when engineers have ideas for things they want to improve, even if they don't align with our existing iteration plans or [OKRs](../../company/okrs). We want to create time and space for engineers to work on these ideas without negatively impacting our team goals and planned work.
We love it when engineers have ideas for things they want to improve, even if they don't align with our existing iteration plans or [OKRs](../../company/okrs/index.md). We want to create time and space for engineers to work on these ideas without negatively impacting our team goals and planned work.
nicksnyder

comment created time in 7 days

Pull request review commentsourcegraph/about

Innovation time

 If there is a dispute about ownership, then perform a [clean escalation](../comm - [VP Engineering](roles.md#vp-engineering) - [Software Engineer](roles.md#software-engineer) +## Innovation time++We love it when engineers have ideas for things they want to improve, even if they don't align with our existing iteration plans or [OKRs](../../company/okrs). We want to create time and space for engineers to work on these ideas without negatively impacting our team goals and planned work.++If you have an idea for something you want to work on, then you have a few options:++1. **Just do it** if you can timebox the effort (e.g., 1-2 days) such that it won't impact your ability to deliver on existing plans.+2. If working on your idea would require a non-trivial amount of time or would impact your ability to deliver on existing plans, then have a discussion with your manager to come up with a feasible plan (e.g., explicitly schedule time to work on your idea during the next iteration).++In any case, you should report the results of your work in [progress updates](tracking_issues#progress-updates) just like any other work.
In any case, you should report the results of your work in [progress updates](tracking_issues.md#progress-updates) just like any other work.
nicksnyder

comment created time in 7 days

push eventsourcegraph/about

Nick Snyder

commit sha c5e4020b9bcc849b543cde2b53b6cd88d332c887

fix formatting

view details

push time in 8 days

PR opened sourcegraph/about

Reviewers
Innovation time

@unknwon started a thread in slack: https://sourcegraph.slack.com/archives/CHPC7UX16/p1593480102102700

Instead of responding there, I decided to propose an update to our handbook.

+11 -0

0 comment

1 changed file

pr created time in 8 days

create barnchsourcegraph/about

branch : innovationtime

created branch time in 8 days

Pull request review commentsourcegraph/about

Add Gonzalo Peci to Team page

 To add yourself to this page, copy the following template, paste it at the end o - Developer Communications - Annapolis, Maryland, USA 🇺🇸 - [laureen@sourcegraph.com](mailto:laureen@sourcegraph.com), [LinkedIn](https://www.linkedin.com/in/laureenhudson/), [GitHub](https://github.com/LaureenH)-- Laureen is a technical and developmental editor; also a storyteller, writer, publisher, enthusiastic geek enabler, autodidact, activist, and instigator. She lives aboard a 47' catamaran with her family, and if she’s not online, it’s probably because she’s crossing an ocean. +- Laureen is a technical and developmental editor; also a storyteller, writer, publisher, enthusiastic geek enabler, autodidact, activist, and instigator. She lives aboard a 47' catamaran with her family, and if she’s not online, it’s probably because she’s crossing an ocean.  ## Christine Lovett (she/her) -- Customer Engineer +- Customer Engineer - New York, NY, USA 🇺🇸 - [christine@sourcegraph.com](mailto:christine@sourcegraph.com), [LinkedIn](https://www.linkedin.com/in/lovettchristine/), [GitHub](https://github.com/christinelovett)-- Christine is a biking, music and general fun enthusiast who likes to balance her travels exploring nature and city. Before Sourcegraph, Christine spent a few years in sales, then software development- ultimately merging her skillset in customer engingeering roles at Docker and Google. She has a strong appreciation for modern development tools and reducing friction in IT. +- Christine is a biking, music and general fun enthusiast who likes to balance her travels exploring nature and city. Before Sourcegraph, Christine spent a few years in sales, then software development- ultimately merging her skillset in customer engingeering roles at Docker and Google. She has a strong appreciation for modern development tools and reducing friction in IT.++## Gonzalo Peci (he/him)++- [Distribution](../../handbook/engineering/distribution/index.md) - Engineering Manager

Yeah, let's defer trying to solve this problem. I agree it is a problem and I would like to find a way to solve it.

pecigonzalo

comment created time in 9 days

PR opened sourcegraph/about

Clarify manager updates
+4 -5

0 comment

1 changed file

pr created time in 9 days

create barnchsourcegraph/about

branch : managerupdateclarifications

created branch time in 9 days

Pull request review commentsourcegraph/careers

Add Engineering Manager - Campaigns

+![logo](https://sourcegraph.com/.assets/img/sourcegraph-light-head-logo.svg)++# Engineering Manager - Campaigns++We are looking for an experienced engineering leader to manage our cross-functional engineering team building [campaigns](https://about.sourcegraph.com/handbook/engineering/campaigns). You will partner with our [product team](https://about.sourcegraph.com/handbook/product) to define team goals, and develop a roadmap to achieve those goals. Our product and team is very technical; we expect you to have a strong background as an engineer so that you can contribute to technical discussions and contribute code when necessary/appropriate. The team is small today but there is a lot more work to be done and we will expect you to grow the team in a sustainable way that maintains our high standards.+

In my opinion

Your opinion is the most important opinion when it comes to hiring a manager for the campaigns team :)

Yes we want a manger who can do code reviews and review RFCs. This is not mutually exclusive with having strong technical leaders on the team who aren't people managers (like yourself).

The term "project lead" was created before we decided to move in the direction of having an engineering manager per mission team, so I expect that name and definition will evolve.

nicksnyder

comment created time in 9 days

issue commentsourcegraph/sourcegraph

Campaigns: 3.18 Tracking Issue

@mrnugget Thanks for the update! I realize that some of the original questions here were repetitive so I updated the docs in the handbook: https://about.sourcegraph.com/handbook/engineering/tracking_issues#progress-updates. So for future updates feel free to to a more informal prose based update based on what you think it is important to communicate about the team's progress.

I also updated the tracking issue template to inline the info that shouldn't change from week to week (what the team is working on and why). Code intel tracking issue is an example of what I am looking for: https://github.com/sourcegraph/sourcegraph/issues/11412

mrnugget

comment created time in 9 days

issue commentsourcegraph/sourcegraph

Code intelligence: 3.18 tracking issue

Thanks for the updates!

I just wanted to share that I really like the format of the updates in these other tracking issues (i.e., more prose less lists):

  • https://github.com/sourcegraph/sourcegraph/issues/11523#issuecomment-651177855
  • https://github.com/sourcegraph/sourcegraph/issues/11494#issuecomment-651120375
  • https://github.com/sourcegraph/sourcegraph/issues/11613#issuecomment-650936066

Handbook docs: https://about.sourcegraph.com/handbook/engineering/tracking_issues#progress-updates

efritz

comment created time in 9 days

issue commentsourcegraph/sourcegraph

Distribution: 3.18 Tracking issue

Thanks for the updates!

I just wanted to share that I really like the format of the updates in these other tracking issues (i.e., more prose less lists):

  • https://github.com/sourcegraph/sourcegraph/issues/11523#issuecomment-651177855
  • https://github.com/sourcegraph/sourcegraph/issues/11494#issuecomment-651120375
  • https://github.com/sourcegraph/sourcegraph/issues/11613#issuecomment-650936066
slimsag

comment created time in 9 days

issue commentsourcegraph/sourcegraph

Web 3.18 Tracking issue

Thanks for the updates!

@twop @felixfbecker @marekweb I just wanted to share that I really like the format of the updates in these other tracking issues (i.e., more prose less lists):

  • https://github.com/sourcegraph/sourcegraph/issues/11523#issuecomment-651177855
  • https://github.com/sourcegraph/sourcegraph/issues/11494#issuecomment-651120375
  • https://github.com/sourcegraph/sourcegraph/issues/11613#issuecomment-650936066
lguychard

comment created time in 9 days

PR opened sourcegraph/about

How to transfer teams

Add some brief docs that if you want to switch teams then just talk to your manager.

Adding these docs because a candidate asked: https://sourcegraph.slack.com/archives/C168VP0FM/p1593451725340400

+4 -0

0 comment

1 changed file

pr created time in 9 days

create barnchsourcegraph/about

branch : switching-teams

created branch time in 9 days

push eventsourcegraph/about

Nick Snyder

commit sha 461fef71a3642cb2ad8e2089f0dbd4ca74f749e6

Add security team responsibilities (#1124)

view details

push time in 9 days

delete branch sourcegraph/about

delete branch : security-team-responsibilities-1

delete time in 9 days

push eventsourcegraph/about

Nick Snyder

commit sha dc490c9785872930407706514afdafdeb226e8a8

Link to real examples for progress updates (#1127)

view details

push time in 9 days

delete branch sourcegraph/about

delete branch : progressupdateexample

delete time in 9 days

create barnchsourcegraph/about

branch : progressupdateexample

created branch time in 9 days

push eventsourcegraph/about

Nick Snyder

commit sha 7a4ebb3d5788079da8158ef47e29ecb5abfd3a3a

Update index.md

view details

push time in 9 days

push eventsourcegraph/about

Nick Snyder

commit sha d8ca30a64af9b06c0e5b7f4c559da09c5bff3ea2

Clarify Loïc's and Nick's involvement in search team (#1122)

view details

push time in 9 days

delete branch sourcegraph/about

delete branch : search-team-manager

delete time in 9 days

push eventsourcegraph/about

Nick Snyder

commit sha 24de86bddbec2ce692c2f01f2b06d890aca7ac3a

Update handbook/engineering/search/index.md

view details

push time in 9 days

Pull request review commentsourcegraph/about

Clarify Loïc's and Nick's involvement in search team

 The search team has divided the responsibilities of a [Project Lead](../roles.md  ## Members -- [Loïc Guychard](../../../company/team/index.md#loic-guychard) (will transition to [engineering manager](../roles.md#engineering-manager) by 2020-07-01) - [Keegan Carruthers-Smith](../../../company/team/index.md#keegan-carruthers-smith) (dividing his time between this team and [cloud](../cloud/index.md)) - [Farhan Attamimi](../../../company/team/index.md#farhan-attamimi) - [Rijnard van Tonder](../../../company/team/index.md#rijnard-van-tonder)+- [Loïc Guychard](../../../company/team/index.md#loic-guychard) is interested in being the [engineering manager](../roles.md#engineering-manager) for this team but is currently focusing his efforts on the [../web/index.md](web team). [Nick Snyder](../../../company/team/index.md#nick-snyder-he-him) will be more involved in the meantime.
- [Loïc Guychard](../../../company/team/index.md#loic-guychard) is interested in being the [engineering manager](../roles.md#engineering-manager) for this team but is currently focusing his efforts on the [web team](../web/index.md). [Nick Snyder](../../../company/team/index.md#nick-snyder-he-him) will be more involved in the meantime.
nicksnyder

comment created time in 9 days

issue commentsourcegraph/sourcegraph

E. S.: On-boarding plan

Yes, I think this is captured by our handbook docs on the security team: https://about.sourcegraph.com/handbook/engineering/security#contact

tsenart

comment created time in 9 days

issue commentsourcegraph/sourcegraph

Search: 3.18 Tracking issue

@attfarhan Thanks for adding the plan section to the description! I think the problem statements could be improved. Right now it reads like problem = !X, solution do X (the problem statement presupposes the solution). Instead, make this problem statement more user focused (e.g., when users do X then run into problem Y. solution => do Z to solve Y).

New Sourcegraph users are not given onramps for successful onboarding.

How do we know this is a problem, what evidence do we have, what exactly is failing?

Users can perform complex and nested search queries to achieve feature parity with OpenGrok.

Why is feature parity with OpenGrok important? (I know that it is, but we need to document why). E.g. customers X and Y (don't say names but link to them in hubspot) decided to not use Sourcegraph because we didn't support Z.

Allow organizations to seamlessly search across contexts of their organizations code

This isn't a problem statement, it is a solution :)

attfarhan

comment created time in 9 days

create barnchsourcegraph/about

branch : security-team-responsibilities-1

created branch time in 9 days

create barnchsourcegraph/about

branch : security-team-responsibilities

created branch time in 9 days

push eventsourcegraph/about

Nick Snyder

commit sha d7e2b735bb137fc2037a0c95f2199e5473c5d000

Update handbook/engineering/search/index.md

view details

push time in 10 days

Pull request review commentsourcegraph/about

Clarify Loïc's and Nick's involvement in search team

 The search team has divided the responsibilities of a [Project Lead](../roles.md  ## Members -- [Loïc Guychard](../../../company/team/index.md#loic-guychard) (will transition to [engineering manager](../roles.md#engineering-manager) by 2020-07-01) - [Keegan Carruthers-Smith](../../../company/team/index.md#keegan-carruthers-smith) (dividing his time between this team and [cloud](../cloud/index.md)) - [Farhan Attamimi](../../../company/team/index.md#farhan-attamimi) - [Rijnard van Tonder](../../../company/team/index.md#rijnard-van-tonder)+- [Loïc Guychard](../../../company/team/index.md#loic-guychard) is interested in being the [engineering manager](../roles.md#engineering-manager) for this team but is currently focusing his efforts on the [../web/index.md](web team). [Nick Snyder](../../../company/team/index.md#nick-snyder-he-him) will be more involved in the meantime.  ## Hiring status  _Updated 2020-06-25_ -- +1 [Software Engineer - Backend](https://github.com/sourcegraph/careers/blob/master/job-descriptions/software-engineer-backend.md)+- +1 [Software Engineer - Backend](https://github.com/sourcegraph/careers/blob/master/job-descriptions/software-engineer-backend.md
- +1 [Software Engineer - Backend](https://github.com/sourcegraph/careers/blob/master/job-descriptions/software-engineer-backend.md)
nicksnyder

comment created time in 10 days

PR opened sourcegraph/about

Reviewers
Clarify Loïc's and Nick's involvement in search team
+2 -2

0 comment

1 changed file

pr created time in 10 days

create barnchsourcegraph/about

branch : search-team-manager

created branch time in 10 days

push eventsourcegraph/sourcegraph

Nick Snyder

commit sha 4028e35505b5f303d06faedc296a886976ee0825

Add plan summary to tracking issue (#11726)

view details

push time in 11 days

delete branch sourcegraph/sourcegraph

delete branch : trackingissue

delete time in 11 days

PR merged sourcegraph/sourcegraph

Reviewers
Add plan summary to tracking issue

Status is in title per updates to https://about.sourcegraph.com/handbook/engineering/tracking_issues#planning-a-milestone-with-a-tracking-issue

+8 -3

2 comments

1 changed file

nicksnyder

pr closed time in 11 days

push eventsourcegraph/sourcegraph

Nick Snyder

commit sha d133f7be4f19a8c2f2e5ee7568032785128fe261

Update .github/ISSUE_TEMPLATE/tracking_issue.md Co-authored-by: Christina Forney <christina@sourcegraph.com>

view details

push time in 13 days

PR opened sourcegraph/sourcegraph

Reviewers
Add plan summary to tracking issue

Status is in title per updates to https://about.sourcegraph.com/handbook/engineering/tracking_issues#planning-a-milestone-with-a-tracking-issue

+8 -3

0 comment

1 changed file

pr created time in 13 days

create barnchsourcegraph/sourcegraph

branch : trackingissue

created branch time in 13 days

push eventsourcegraph/about

Nick Snyder

commit sha b50e93695e7b016aeec3ec99b8d8c962b397eceb

Weekly updates from each engineering team (#1083)

view details

push time in 13 days

delete branch sourcegraph/about

delete branch : engroles

delete time in 13 days

PR merged sourcegraph/about

Weekly updates from each engineering team

I have lost touch with what the engineering team is doing. It started with me not attending team syncs and it finished with removing eng updates to company meetings. I need to regain this context.

My needs:

  • I need to understand what each team’s goals and priorities are at any given point in time.
    • Why?
      • So I can ensure that we have the right goals and priorities (i.e., they are aligned with our others functions like sales/product).
  • I need to know what work each team is doing and how it connects back to those goals.
    • Why?
      • So I can hold the team accountable for doing work that is actually in service of those goals.
  • I need to know what pain teams and engineers are experiencing (e.g., gaps in ownership, gaps in infrastructure)
    • Why?
      • So I can ensure we are making the right investments, both in terms of people and in infrastructure.
  • Meta: I need to know/verify that the leader of each team knows all of the above too.
    • Why?
      • So I can have trust that our team leads are on top of things and doing a good job.
      • So I have a single source of truth for this information for each team.

What won’t work:

  • Me attending team syncs. This doesn’t scale well for me because they are fixed time blocks on my calendar and I will become a scheduling bottleneck across all teams (e.g., me attending all will mean none can happen concurrently). I also need to keep calendar time open to be available for candidate calls.
  • Adding eng slides back to company meeting. The level of detail that I need is not relevant to the entire company every week anymore.

This PR is my proposed solution: weekly updates from each engineering team. Campaigns -> @mrnugget Search -> @attfarhan Cloud -> @tsenart Web -> @lguychard Distribution -> @slimsag (this replaces our live sync on Mondays) until Gonzalo picks this up Code intel -> me

I know some of you aren't managers, but I still need this information and I need to you step up in the meantime as I hire :)

+34 -23

2 comments

2 changed files

nicksnyder

pr closed time in 13 days

pull request commentsourcegraph/about

Weekly updates from each engineering team

Going to merge because I think this is better than what is in master, but I will gladly accept feedback and address it in a future PR.

nicksnyder

comment created time in 13 days

push eventsourcegraph/about

Nick Snyder

commit sha 2b420f93f777bd4191b04bfb9cba6e9f1a541a81

fix formatting

view details

push time in 13 days

Pull request review commentsourcegraph/about

Weekly updates from each engineering team

 Some teams with more experienced members may need less guidance in certain areas ### Responsibilities  - Directly contribute through code, RFCs or PR reviews for a minimum of roughly 50% of their time.-- Collaborate with [product](../product/index.md) to maintain a [prioritized roadmap](../../direction/index.md) for the work owned by their team as well as quarterly [OKRs](../../company/okrs/index.md)-- Plan and commit to a set of work that will be accomplished by the team for each [monthly release](releases/index.md) and capture those commitments in a [tracking issue](tracking_issues.md) on GitHub.+- Ensure that the team has a roadmap that documents how it is going to achieve its [OKRs](../../company/okrs/index.md).+- Ensure the the team's [tracking issue](tracking_issues.md) captures the work that each teammate has committed to for each [monthly release](releases/index.md).+- Post a weekly update by EOD Monday on the tracking issue that answers the following questions:+  1. What work did the team do last week?+    - This is a summary not details. The details should exist in each teammate's individual update and shouldn't be repeated.+  1. How does that work connect back to the team’s OKRs and roadmap?+  1. For each OKR and roadmap item, is the team on track? The answer should be of the form:+    - We expect to reach this goal.+    - We are at risk of not reaching this goal because A, B, C.+      - What can we change to get this back on track?+    - We are not going to reach this goal because A, B, C.+      - What did we learn from this failure to achieve our goals?+  1. What did the team work on last week that wasn’t originally planned? Why?

I moved the docs to the tracking issue page and updated the wording. PTAL and suggest any edits that you think would make it more clear.

nicksnyder

comment created time in 13 days

Pull request review commentsourcegraph/about

Weekly updates from each engineering team

 Some teams with more experienced members may need less guidance in certain areas ### Responsibilities  - Directly contribute through code, RFCs or PR reviews for a minimum of roughly 50% of their time.-- Collaborate with [product](../product/index.md) to maintain a [prioritized roadmap](../../direction/index.md) for the work owned by their team as well as quarterly [OKRs](../../company/okrs/index.md)-- Plan and commit to a set of work that will be accomplished by the team for each [monthly release](releases/index.md) and capture those commitments in a [tracking issue](tracking_issues.md) on GitHub.+- Ensure that the team has a roadmap that documents how it is going to achieve its [OKRs](../../company/okrs/index.md).+- Ensure the the team's [tracking issue](tracking_issues.md) captures the work that each teammate has committed to for each [monthly release](releases/index.md).+- Post a weekly update by EOD Monday on the tracking issue that answers the following questions:+  1. What work did the team do last week?+    - This is a summary not details. The details should exist in each teammate's individual update and shouldn't be repeated.+  1. How does that work connect back to the team’s OKRs and roadmap?+  1. For each OKR and roadmap item, is the team on track? The answer should be of the form:

I moved the docs to the tracking issue page and updated the wording. PTAL and suggest any edits that you think would make it more clear.

nicksnyder

comment created time in 13 days

Pull request review commentsourcegraph/about

Weekly updates from each engineering team

 # Roles on the Engineering team -This page lists the roles on the Engineering team and some of the responsibilities for each of the roles.+This page lists the roles on our engineering team.  ## Software Engineer -Software Engineers are individual contributors who build software to satisfy the needs of the business.+Software engineers build our product and infrastructure.  ### Responsibilities -- Collaborate with your direct manager to identify projects that align your skills and interests with the needs of the business.-- Write [RFCs](../communication/rfcs/index.md) to recommend solutions to product and engineering problems. - Commit to a reasonable amount of work that you are going to get done for each [monthly release](releases/index.md), and then reliably get it done.+- Post weekly updates about your progress on the [monthly release tracking issue](tracking_issues.md) for your team.

Yep, added

nicksnyder

comment created time in 13 days

Pull request review commentsourcegraph/about

Weekly updates from each engineering team

 Some teams with more experienced members may need less guidance in certain areas ### Responsibilities  - Directly contribute through code, RFCs or PR reviews for a minimum of roughly 50% of their time.-- Collaborate with [product](../product/index.md) to maintain a [prioritized roadmap](../../direction/index.md) for the work owned by their team as well as quarterly [OKRs](../../company/okrs/index.md)-- Plan and commit to a set of work that will be accomplished by the team for each [monthly release](releases/index.md) and capture those commitments in a [tracking issue](tracking_issues.md) on GitHub.+- Ensure that the team has a roadmap that documents how it is going to achieve its [OKRs](../../company/okrs/index.md).+- Ensure the the team's [tracking issue](tracking_issues.md) captures the work that each teammate has committed to for each [monthly release](releases/index.md).+- Post a weekly update by EOD Monday on the tracking issue that answers the following questions:+  1. What work did the team do last week?+    - This is a summary not details. The details should exist in each teammate's individual update and shouldn't be repeated.+  1. How does that work connect back to the team’s OKRs and roadmap?+  1. For each OKR and roadmap item, is the team on track? The answer should be of the form:+    - We expect to reach this goal.+    - We are at risk of not reaching this goal because A, B, C.+      - What can we change to get this back on track?+    - We are not going to reach this goal because A, B, C.+      - What did we learn from this failure to achieve our goals?+  1. What did the team work on last week that wasn’t originally planned? Why?+  1. What pain is the team experiencing? - Help keep the team focused on their goals while keeping them aware of the higher level picture. - Identify blockers or productivity issues and work with the team to address them. - Run weekly team sync meetings. - Communicate progress to stakeholders and other parts of the company (e.g. at company meeting). - Conduct monthly [retrospectives](../../retrospectives/index.md) with their team. - Scale themselves out by organizing and delegating work to other teammates. - Mentor and coach other teammates with timely feedback as appropriate in order to uphold team values and help them grow.-- Collaborate with Engineering Managers to ensure team mates have everything they need to succeed and deliver on the goals of the team.+- Collaborate with engineering managers to ensure teammates have everything they need to succeed and deliver on the goals of the team.  ## Engineering Manager -Engineering Managers are people managers who build teams of [Software Engineers](#software-engineer) to satisfy the needs of the business.+Engineering managers lead, grow, and develop teams of software engineers.  ### Responsibilities -- Collaborate with [product](../product/index.md) to maintain a [prioritized roadmap](../../direction/index.md) for the work owned by your team.-- Commit to a set of work that will be accomplished by the team for each [monthly release](releases/index.md) and capture those commitments in a [tracking issue](tracking_issues.md) on GitHub.-- Conduct monthly [retrospectives](../../retrospectives/index.md) with your team.-- Mentor and coach engineers through regular [1-1s](../leadership/1-1.md) to grow their careers.-- [Review the performance](../people-ops/review-cycles.md) of your direct reports to determine compensation.-- Interview candidates and own making improvements to our hiring process.-- Review applications and make final hiring decisions for candidates interested in your team.+Build an exceptional team that achieves results.++- Ensure that the team has a roadmap that documents how it is going to achieve its [OKRs](../../company/okrs/index.md).+- Ensure the the team's [tracking issue](tracking_issues.md) captures the work that each teammate has committed to for each [monthly release](releases/index.md).+- Post a weekly update by EOD Monday on the tracking issue that answers the following questions:

Yep, I moved this doc to the tracking issue page.

nicksnyder

comment created time in 13 days

Pull request review commentsourcegraph/about

Weekly updates from each engineering team

 # Roles on the Engineering team -This page lists the roles on the Engineering team and some of the responsibilities for each of the roles.+This page lists the roles on our engineering team.  ## Software Engineer -Software Engineers are individual contributors who build software to satisfy the needs of the business.+Software engineers build our product and infrastructure.  ### Responsibilities -- Collaborate with your direct manager to identify projects that align your skills and interests with the needs of the business.-- Write [RFCs](../communication/rfcs/index.md) to recommend solutions to product and engineering problems. - Commit to a reasonable amount of work that you are going to get done for each [monthly release](releases/index.md), and then reliably get it done.+- Post weekly updates about your progress on the [monthly release tracking issue](tracking_issues.md) for your team.

Yes we should. I just updated the tracking issue docs.

nicksnyder

comment created time in 13 days

more