Dec 6 - 10, 2021

Register for Free
Scaling Knowledge > Scaling Bodies: Why dbt Labs is making the bet on a data literate organization

Scaling Knowledge > Scaling Bodies: Why dbt Labs is making the bet on a data literate organization - Erica Louie

Keynote: How big is this wave? Keynote: How big is this wave?

Keynote: How big is this wave? - Martin Casado & Tristan Handy

dbt 101: Stories from real-life data practitioners + a live look at dbt dbt 101: Stories from real-life data practitioners + a live look at dbt

dbt 101: Stories from real-life data practitioners + a live look at dbt - Natty (Jon Natkins) & Alexis Wong Baird

How to build a mature dbt project from scratch

How to build a mature dbt project from scratch - Dave Connors

Analytics Engineering for storytellers

Analytics Engineering for storytellers - Winnie Winship

The modern data experience

The modern data experience - Benn Stancil

Identity Crisis: Navigating the Modern Data Organization Identity Crisis: Navigating the Modern Data Organization Identity Crisis: Navigating the Modern Data Organization Identity Crisis: Navigating the Modern Data Organization Identity Crisis: Navigating the Modern Data Organization

Identity Crisis: Navigating the Modern Data Organization - Jillian Corkin, David Jayatillake, Caitlin Moorman, Barr Moses & Stefania Olafsdottir

Git for the rest of us

Git for the rest of us - Claire Carroll

You don’t need another database: A conversation with Reynold Xin (Databricks) and Drew Banin (dbt Labs) You don’t need another database: A conversation with Reynold Xin (Databricks) and Drew Banin (dbt Labs)

You don’t need another database: A conversation with Reynold Xin (Databricks) and Drew Banin (dbt Labs) - Drew Banin & Reynold Xin

Share. Empower. Repeat. Come learn about how to become a Meetup Organizer!

Share. Empower. Repeat. Come learn about how to become a Meetup Organizer! - Rosie Cardoso

The Operational Data Warehouse: Reverse ETL, CDPs, and the future of data activation

The Operational Data Warehouse: Reverse ETL, CDPs, and the future of data activation - Tejas Manohar

Refactor your hiring process: a framework (Workshop Sponsor) Refactor your hiring process: a framework (Workshop Sponsor) Refactor your hiring process: a framework (Workshop Sponsor)

Refactor your hiring process: a framework (Workshop Sponsor) - Ilse Ackerman, Ezinne Chimah & Rocío Garza Tisdell

Tailoring dbt's incremental_strategy to Artsy's data needs

Tailoring dbt's incremental_strategy to Artsy's data needs - Abhiti Prabahar

Optimizing query run time with materialization schedules

Optimizing query run time with materialization schedules - Ola Canty

How dbt Enables Systems Engineering in Analytics

How dbt Enables Systems Engineering in Analytics - Jorge Cruz Serralles

When to ask for help: Modern advice for working with consultants in data and analytics

When to ask for help: Modern advice for working with consultants in data and analytics - Jacob Frackson

Smaller Black Boxes: Towards Modular Data Products

Smaller Black Boxes: Towards Modular Data Products - Stephen Bailey

The Modern Data Stack: How Fivetran Operationalizes Data Transformations

The Modern Data Stack: How Fivetran Operationalizes Data Transformations - Nick Acosta

Analytics Engineering Everywhere: Why in Five Years Every Organization Will Adopt Analytics Engineering

Analytics Engineering Everywhere: Why in Five Years Every Organization Will Adopt Analytics Engineering - Jason Ganz

Down with

Down with "data science" - Emilie Schario

So You Think You Can DAG: Supporting data scientists with dbt packages

So You Think You Can DAG: Supporting data scientists with dbt packages - Emma Peterson

Operationalizing Column-Name Contracts with dbtplyr

Operationalizing Column-Name Contracts with dbtplyr - Emily Riederer

Data Paradox of the Growth-Stage Startup

Data Paradox of the Growth-Stage Startup - Emily Ekdahl

Batch to Streaming in One Easy Step Batch to Streaming in One Easy Step

Batch to Streaming in One Easy Step - Emily Hawkins & Arjun Narayan

The Call is Coming from Inside the Warehouse: Surviving Schema Changes with Automation The Call is Coming from Inside the Warehouse: Surviving Schema Changes with Automation

The Call is Coming from Inside the Warehouse: Surviving Schema Changes with Automation - Lewis Davies & Erika Pullum

Beyond the Box: Stop relying on your Black co-worker to help you build a diverse team.

Beyond the Box: Stop relying on your Black co-worker to help you build a diverse team. - Akia Obas

Observability Within dbt Observability Within dbt

Observability Within dbt - Kevin Chan & Jonathan Talmi

Inclusive Design and dbt

Inclusive Design and dbt - Evelyn Stamey

Built It Once & Build It Right: Prototyping for Data Teams

Built It Once & Build It Right: Prototyping for Data Teams - Alex Viana

Coalesce After Party with Catalog & Cocktails Coalesce After Party with Catalog & Cocktails

Coalesce After Party with Catalog & Cocktails - Tim Gasper & Juan Sequeda

How to Prepare Data for a Product Analytics Platform (Workshop Sponsor)

How to Prepare Data for a Product Analytics Platform (Workshop Sponsor) - Esmeralda Martinez

Toward a Polyglot Environment for Analytics

Toward a Polyglot Environment for Analytics - Caitlin Colgrove

Automating Ambiguity: Managing dynamic source data using dbt macros

Automating Ambiguity: Managing dynamic source data using dbt macros - Eric Nelson

The Endpoints are the Beginning: Using the dbt Cloud API to build a culture of data awareness

The Endpoints are the Beginning: Using the dbt Cloud API to build a culture of data awareness - Kevin Hu

Data as Engineering

Data as Engineering - Raazia Ali

Building On Top of dbt: Managing External Dependencies

Building On Top of dbt: Managing External Dependencies - Teghan Nightengale

Data Analytics in a Snowflake world: A conversation with Christian Kleinerman and Tristan Handy Data Analytics in a Snowflake world: A conversation with Christian Kleinerman and Tristan Handy

Data Analytics in a Snowflake world: A conversation with Christian Kleinerman and Tristan Handy - Tristan Handy & Christian Kleinerman

Keynote: Building a Force of Gravity

Keynote: Building a Force of Gravity - Drew Banin

dbt Core v1.0 Reveal ✨

dbt Core v1.0 Reveal ✨ - Jeremy Cohen

Firebolt Deep Dive - Next generation performance with dbt Firebolt Deep Dive - Next generation performance with dbt

Firebolt Deep Dive - Next generation performance with dbt - Kevin Marr & Cody Schwarz

dbt, Notebooks and the modern data experience dbt, Notebooks and the modern data experience

dbt, Notebooks and the modern data experience - Allan Campopiano & Elizabeth Dlha

No silver bullets: Building the analytics flywheel No silver bullets: Building the analytics flywheel No silver bullets: Building the analytics flywheel

No silver bullets: Building the analytics flywheel - Kelly Burdine, Lewis Davies & Erika Pullum

Don't hire a data engineer...yet

Don't hire a data engineer...yet - Stefania Olafsdottir

dbt for Financial Services: How to boost returns on your SQL pipelines using dbt, Databricks, and Delta Lake

dbt for Financial Services: How to boost returns on your SQL pipelines using dbt, Databricks, and Delta Lake - Ricardo Portilla

The Future of Data Analytics The Future of Data Analytics The Future of Data Analytics The Future of Data Analytics

The Future of Data Analytics - Sarah Catanzaro, Jennifer Li, Astasia Myers & Julia Schottenstein

Implementing and scaling dbt Core without engineers

Implementing and scaling dbt Core without engineers - Elliot Wargo

Building an Open Source Data Stack

Building an Open Source Data Stack - Katie Hindson

This is just the beginning

This is just the beginning - Alan Cruickshank

dbt in a data mesh world

dbt in a data mesh world - José Cabeda

Introducing the activity schema: data modeling with a single table

Introducing the activity schema: data modeling with a single table - Ahmed Elsamadisi

From Diverse

From Diverse "Humans of Data" to Data Dream "Teams" - Prukalpa Sankar

From 100 spreadsheets to 100 data analysts: the story of dbt at Slido From 100 spreadsheets to 100 data analysts: the story of dbt at Slido From 100 spreadsheets to 100 data analysts: the story of dbt at Slido

From 100 spreadsheets to 100 data analysts: the story of dbt at Slido - Daniela Barokova, Michal Kolacek & Andrej Svec

To All The Data Managers We've Loved Before To All The Data Managers We've Loved Before

To All The Data Managers We've Loved Before - Paige Berry & Adam Stone

Stay Calm and Query on: Root Cause Analysis for Your Data Pipelines (Workshop Sponsor)

Stay Calm and Query on: Root Cause Analysis for Your Data Pipelines (Workshop Sponsor) - Francisco Alberini

Upskilling from an Insights Analyst to an Analytics Engineer

Upskilling from an Insights Analyst to an Analytics Engineer - Brittany Krauth

Modeling event data at scale (Workshop Sponsor)

Modeling event data at scale (Workshop Sponsor) - Will Warner

Building a metadata ecosystem with dbt

Building a metadata ecosystem with dbt - Darren Haken

New Data Role on the Block: Revenue Analytics

New Data Role on the Block: Revenue Analytics - Celina Wong

Using dbt to understand open-source communities

Using dbt to understand open-source communities - Srini Kadamati

Getting Meta about Metadata: Building Trustworthy Data Products Backed by dbt (Workshop Sponsor) Getting Meta about Metadata: Building Trustworthy Data Products Backed by dbt (Workshop Sponsor)

Getting Meta about Metadata: Building Trustworthy Data Products Backed by dbt (Workshop Sponsor) - Angie Brown & Kelechi Erondu

🍪 Eat the data you have: tracking core events in a cookieless world

🍪 Eat the data you have: tracking core events in a cookieless world - Jeff Sloan

Trials and Tribulations of Incremental Models

Trials and Tribulations of Incremental Models - Vincey Au

Sharing the knowledge - joining dbt and

Sharing the knowledge - joining dbt and "the Business" using Tāngata - Chris Jenkins

SQL Draw Artworks Review Panel

SQL Draw Artworks Review Panel - James Weakley

dbt Community Code of Conduct

dbt has a supportive, active community of thousands of smart, kind, and helpful people who share a commitment to elevating the analytics profession.

You can get involved in the dbt community by connecting at events, getting or giving help in any of our many channels, contributing to dbt or a dbt package, and many other ways.

People genuinely love this community, and we are committed to maintaining the spirit of it. As such have written this Code of Conduct to help all participants understand how to best participate in our community.

The Code of Conduct applies to all dbt Community spaces both online and off. This includes: Slack, Discourse, code repositories (dbt Core, dbt packages etc), Office Hours and Meetups. There are some guidelines specific to particular forums (listed below). Participants are responsible for knowing and abiding by this Code of Conduct.

This Code of Conduct has three sections:

  • dbt Community Values: These values apply to all of our community spaces, and all of our guidelines are based on these values.
  • Forum-specific guidelines: These guidelines explain some of the cultural norms that apply to specific forums.
  • Anti-harassment policy: We are dedicated to providing a harassment-free experience for everyone in our community — here, we outline exactly what that means.

We appreciate your support in continuing to build a community we’re all proud of.

— The dbt Community Admin Team.

dbt Community Values #

Be respectful. #

We want everyone to have a fulfilling and positive experience in the dbt Community and we are continuously grateful in your help ensuring that this is the case.

Be courteous, respectful, and polite to fellow community members. Generally, don’t be a jerk.

Be considerate of others’ time — many people in the community generously give their time for free.

Ways to demonstrate this value:

  • Take the time to write bug reports well (example)
  • Thank people if they help solve a problem.

Be you. #

Some developer communities allow and even encourage anonymity — we prefer it when people identify themselves clearly. It helps to build empathy, and form relationships.

Ways to demonstrate this value:

  • Update your profile on any dbt Community forums to include your name, and a clear picture. On Slack, use the “what I do” section to add your role title and current company
  • Write in your own voice, and offer your own advice, rather than speaking in your company’s marketing or support voice.

Encourage diversity and participation. #

People with different mindsets and experiences, working together, create better outcomes. This includes diversity of race and gender, as well as the diversity of academic and career backgrounds, socio-economic backgrounds, geographic backgrounds, ideologies, and interests.

Ways to demonstrate this value:

  • Make everyone in our community feel welcome, regardless of their background, and do everything possible to encourage participation in our community.
  • Demonstrate empathy for a community member’s experience — not everyone comes from the same career background, so adjust answers accordingly.
  • If you are sourcing speakers for events, put in additional effort to find speakers from underrepresented groups.

Create more value than you capture. #

Each community member should strive to create more value in the community than they capture. This is foundational to being a community.

Ways to demonstrate this value:

  • Contribute to dbt or a dbt package
  • Participate in discussions on Slack and Discourse
  • Share things you have learned on Discourse
  • Host events

Be curious. #

Always ask yourself “why?” and strive to be continually learning.

Ways to demonstrate this value:

  • Try solving a problem yourself before asking for help, e.g. rather than asking “what happens when I do X”, experiment and observe the results!
  • When asking questions, explain the “why” behind your decisions, e.g. “I’m trying to solve X problem, by writing Y code. I’m getting Z problem”
  • When helping someone else, explain why you chose that solution, or if no solution exists, elaborate on the reason for that, e.g. “That’s not possible in dbt today — but here’s a workaround / check out this GitHub issue for a relevant discussion”

Guidelines #

Participating in Slack #

dbt Slack is where the dbt community hangs out, discusses issues, and troubleshoots problems together. It is not a support service — please do not treat it like one.

We also have a number of cultural norms in our Slack community. You must read and agree to the rules before joining Slack, but you can also find them here.

As a short summary:

Vendor guidelines #

If you are a vendor (i.e. you represent an organization that sells a product or service relevant to our community), then there are additional guidelines you should be aware of.

Most importantly — do not solicit members of our community as lead generation. You can find the rest of these here.

Guideline violations — 3 strikes method #

The point of our guidelines is not to find opportunities to punish people, but we do need a fair way to deal with people who do harm to our community. Violations related to our anti-harassment policy (below) will be addressed immediately and are not subject to 3 strikes.

  1. First occurrence: We’ll give you a friendly, but public, reminder that the behavior is inappropriate according to our guidelines.
  2. Second occurrence: We’ll send you a private message with a warning that any additional violations will result in removal from the community.
  3. Third occurrence: Depending on the violation, we might need to delete or ban your account.

Notes:

  • Obvious spammers are banned on first occurrence.
  • Participation in the dbt Community is a privilege — we reserve the right to remove people from the community.
  • Violations are forgiven after 6 months of good behavior, and we won’t hold a grudge.
  • People who are committing minor formatting / style infractions will get some education, rather than hammering them in the 3 strikes process.
  • Contact conduct@getdbt.com to report abuse or appeal violations. In the case of appeals, we know that mistakes happen, and we’ll work with you to come up with a fair solution if there has been a misunderstanding.

Anti-harassment policy #

Further to our guidelines for participating in the community in a positive manner, we are also dedicated to providing a harassment-free experience for everyone. We do not tolerate harassment of participants in any form.

Harassment includes:

  • Offensive comments related to gender, gender identity and expression, sexual orientation, disability, mental illness, neuro(a)typicality, physical appearance, body size, age, race, or religion.
  • Unwelcome comments regarding a person’s lifestyle choices and practices, including those related to food, health, parenting, drugs, and employment.
  • Deliberate misgendering or use of ‘dead’ or rejected names.
  • Gratuitous or off-topic sexual images or behaviour in spaces where they’re not appropriate.
  • Physical contact and simulated physical contact (eg, textual descriptions like “hug” or “backrub”) without consent or after a request to stop.
  • Threats of violence.
  • Incitement of violence towards any individual, including encouraging a person to commit suicide or to engage in self-harm.
  • Deliberate intimidation.
  • Stalking or following.
  • Harassing photography or recording, including logging online activity for harassment purposes.
  • Sustained disruption of discussion.
  • Unwelcome sexual attention.
  • Pattern of inappropriate social contact, such as requesting/assuming inappropriate levels of intimacy with others
  • Continued one-on-one communication after requests to cease.
  • Deliberate “outing” of any aspect of a person’s identity without their consent except as necessary to protect vulnerable people from intentional abuse.
  • Publication of non-harassing private communication.

The dbt Community prioritizes marginalized people’s safety over privileged people’s comfort. The dbt Community Admin team reserves the right not to act on complaints regarding:

  • ‘Reverse’ -isms, including ‘reverse racism,’ ‘reverse sexism,’ and ‘cisphobia’
  • Reasonable communication of boundaries, such as “leave me alone,” “go away,” or “I’m not discussing this with you.”
  • Communicating in a ‘tone’ you don’t find congenial
  • Criticizing racist, sexist, cissexist, or otherwise oppressive behavior or assumptions

Reporting harassment #

If you are being harassed by a member of the dbt Community, notice that someone else is being harassed, or have any other concerns, please contact us at conduct@getdbt.com.

We will respect confidentiality requests for the purpose of protecting victims of abuse. At our discretion, we may publicly name a person about whom we’ve received harassment complaints, or privately warn third parties about them, if we believe that doing so will increase the safety of dbt community members or the general public. We will not name harassment victims without their affirmative consent.

Consequences #

Participants asked to stop any harassing behavior are expected to comply immediately.

If a participant engages in harassing behavior, the dbt Community Admin team may take any action they deem appropriate, up to and including expulsion from all dbt Community spaces and identification of the participant as a harasser to other dbt Community members or the general public.

Credits #

Credit to 01.org, Tizen.org, and Geek Feminism for some of the wording used in this Code of Conduct.