Dev Experience team
The Dev Experience team, or DevX for short, is a team focused on improving the developer experience of Sourcegraph.
Members
- Quinn Hare, Product Manager
- Kristen Stretch, Engineering Manager, Developer Experience
- Dave Try, Software Engineer
- Marek Zaluski, Software Engineer
- Manuel Ucles, Software Engineer
- JH Chabran, Software Engineer
- Sander Ginn, Software Engineer
- William Bezuidenhout, Software Engineer
- Kalan Chan, Software Engineer
Strategy
Find out more about the Dev Experience team’s mission, vision, and strategic plans in our Strategy page.
Responsibilities
- General
- Monitoring and triaging
dx
issues and project board - Dev experience support
- Monitoring and triaging
- Tooling
- Backend platform
lib/errors
: error types for Sourcegraph backend servicessourcegraph/log
: standardized logging for Sourcegraph backend services + how-to guidesourcegraph/run
: execute commands and manipulate command output in Go experimentinternal/observation
: all-in-one operation-oriented observability primitives + how-to guideinternal/trace
,internal/tracer
: tracing infrastructure and libraries- Packaging infrastructure (e.g. base Docker images)
- SOC2 compliance regarding software development lifecycles, testing, and continuous integration
- Continuous integration (also see CI support responsibilities)
- Other
- Developer experience newsletter
sg
hack hour- GCP cost and cost reduction initiatives
Also see org-wide areas of ownership and our team processes.
Contact
- Discussions and questions: #dev-experience channel, @dev-experience, and developer experience GitHub discussions
- Support:
@dev-experience-support
in Slack - GitHub: team/dev-experience label and @sourcegraph/dev-experience team.
- We also monitor and track issues with the dx label in our GitHub project.
Principles
We inherit Sourcegraph’s engineering principles and practices. In addition, the following principles guide the work we do in dev experience. Sometimes adhering to one causes us to compromise another, but they guide our decisions on what matters.
- We don’t own the developer experience at Sourcegraph – we simply focus on it. Sourcegraph engineers own the developer experience as a collective.
- We ship open products. Our products are open to contributions to anyone in the company, documented, and provide migration paths if necessary. Our decisions are clearly and publicly communicated for everyone to understand our reasoning. We want to make it simple for everyone to benefit from and work on Sourcegraph’s developer experience.
- We bandage first, then plan for surgery. Fix local problems first, then generalize if and only if it makes sense.
- What we cannot take upon right now, we make its status clear and provide stewardship.
- We should never refuse to fix a “now” problem in favour of a long-term solution, only to cancel the fix because the priorities changed in between. More than not addressing the issue at hand, it prevents our users from fixing the problem for themselves in the meantime.
- We deliver small and iterative experiments and collect feedback. We communicate regularly on their status to enable others to provide inputs. We should reap the benefits of what we work on as we go, not at the end.
- What we cannot take upon right now, we make its status clear and provide stewardship.
- We listen and observe. Our users often know best what’s immediately good for them because they are the ones experiencing it every day. We are not a dependency. We actively seek to avoid blocking product teams. We focus on improving and expediting progress, not being critical to it.
Processes
Read more about how this team works.
Useful resources
- Tools and languages updates feed is available in #dev-experience-notifications
- GitHub issues and pull-requests feed is available in #dx-github-feed
- Alerts in #dev-experience-alerts
- DevX initiatives code insights
- devx-scratch
Growth plan
Come work with us! We’re hiring software engineers to join our team in and - check out our careers page!
Tech stack
We primarily build tools and libraries in Go, with a dash of bash scripting in between. We also operate CI infrastructure with Kubernetes and Terraform.