While in San Francisco last month, I had the honor of presenting at the dbt Community meetup. My talk was titled “Committing To Documentation Can Change Your (Work) Life: The GitLab Data Team’s Approach”.
When we talk about documentation there is an inevitable groan. In this talk, Emilie Schario of GitLab will share how the team’s commitment to documentation has supported headcount 5x-ing in less than a year. She’ll share three principles you can apply to documentation that can help set your team up for success. Emilie was the first Data Analyst at GitLab and has a built a career around being the first data analyst at growth-oriented startups. She is currently the Data Engineer specializing in Analytics. She is an Army Wife and Princeton University and Venture for America alumna. She currently lives in Savannah, GA.
The GitLab data team is a phenomenal place to work. Our commitment to transparency means all our work is available and public. Here are the links I love to highlight:
- our primary page in the GitLab handbook
- our dbt docs
- our project (repository)
In a recent blog post 4 Examples of the Power of Open Source Analytics, my colleague Staff Data Engineer, Architecture Taylor Murphy wrote “the actual code that you use for analytics isn’t your company’s competitive advantage.” While I didn’t realize just how much, working at GitLab has 100% convinced me this is true. GIGO (Garbage in, Garbage out) has a new meaning when you know that retention(whether is financial or product) is all the same analyses, but the quality of the data input is more important than the quality of the code on the page.
The key take way from this talk are our three principles about documentation:
- Documenting (and testing) is part of developing, not an after thought
- Document early and often
- Everyone can contribute
There were two other presentations that night- how Envoy (our wonderful hosts!) wrangled their dbt project and what is coming next for dbt. I am most excited for warn & error test failures in 0.14.0.