Developer Tooling team

Mission

• Build state-of-the-art developer tools that are efficient and reliable, empowering developers to keep their development environments up-to-date painlessly.
• Enable contributors to contribute to our tools.
• Measure what matters: improvements in developer experience, efficiency, and toil reduction, using both quantitative and qualitative metrics.

Vision

The Developer Tooling team’s vision is to create tools that enable GitLab team members and the wider community to contribute to GitLab efficiently, without the friction and manual toil that often come with working on large, complex software projects like GitLab.

Areas of responsibilities

flowchart LR
    DT[Developer Tooling] --focuses on--> GDK[GitLab Development Kit]
    click GDK "https://gitlab.com/gitlab-org/gitlab-development-kit"
    GDK --> GDKRemoteDev[GDK remote development workspace]

    DT --> CanonicalTooling[gitlab-org/gitlab tooling]

    CanonicalTooling --> StaticAnalysis[Static Analysis]

    DT --> AuxTooling[Auxiliary tooling<br><small>Useful tools for GitLab.com.</small>]
    AuxTooling --> civiz[Pipeline Visualizer]
    AuxTooling --> subparticle[Subparticle]

    click civiz "https://gitlab.com/gitlab-org/quality/engineering-productivity/pipeline-visualizer"
    click subparticle "https://gitlab.com/gitlab-org/quality/engineering-productivity/subparticle"

Team structure

Members

Team Members	Role
Vincy Wilson	Acting Engineering Manager
Nao Hashizume	Backend Engineer, Developer Tooling
Kev Kloss	Frontend Engineer, Developer Tooling
Peter Leitzen	Staff Backend Engineer, Developer Tooling

Stable counterpart

Person	Role
Greg Alfaro	GDK Project Stable Counterpart, Application Security

OKRs

Objectives and Key Results (OKRs) help align our sub-department towards what really matters. These happen quarterly and are based on company OKRs. We follow the OKR process defined here.

Here is an overview of our current OKRs.

Communication

View page source - Edit this page - please contribute.