The goal of a Deep Dive session is to share knowledge about a particular topic, with the assumption that recipients already have some basic understanding or aptitude for the given subject. This aligns with how we work since everything at GitLab is public by default. This is a particularly useful initiative within Engineering teams to mitigate dependencies between specific engineers and areas of the codebase, while also improving collaboration and product knowledge with the wider group. An example format guideline:
Note: The support team have documented similar initiatives in the handbook: Support Deep Dives and Support Training Modules.
If you're new to presenting at GitLab the steps can be a bit daunting. The steps are mostly documented elsewhere in the handbook, but are summarized here to give an overview.
At a minimum it usually makes sense to invite your team to the session, but you may also want to invite other teams if you feel the topic is particularly relevant to them (e.g. you may want to invite the Security team if you're discussing authentication).
#whats-happening-at-gitlabon slack including the zoom/presentation links.
Upload it to YouTube: