Level Up - Building High performing team culture

Level Up - Building High performing team culture

What does it mean to strive for ENGINEERING EXCELLENCE? As your engineering organization grows, you want to encourage teams and individuals to develop and improve their technical proficiency and practices. Growth puts stress on your teams' ability to deliver kick-ass code consistently. To help them improve and grow, we built the LEVEL UP model to represent everything that's expected of an excellent engineering team.

In this talk, I’ll review why we built this model, refined it and how we got teams to adopt it and the effects that it had on our department. I will also give you the tools to either use our model or fork your own specific one for your organization.

2f7eb8e439ce2d288dcfa240b5210664?s=128

Yonatan Bergman

June 16, 2019
Tweet

Transcript

  1. 5.

    Sam Altman
 @sama If you notice something at your company

    below standards and don't fix it or make sure someone else does, you have set a new standard. Complaining about it does not count as fixing it.
  2. 8.

    @yonbergman 46 TIMES MORE 2,555 TIMES FASTER 7 TIMES LOWER

    2,604 TIMES FASTER DEPLOYMENTS LEAD TIME FAILURE RATE TIME TO RECOVER
  3. 15.

    @yonbergman –@mipsytipsy “It's about software ownership…
 Align your incentives so

    that the people who break the deploy are the people who feel the pain, and the rest will more or less fall into place”
  4. 22.
  5. 31.
  6. 34.

    @yonbergman LEVEL UP - TRACKS • Design & Architecture •

    Writing Quality Code • Testing • Rolling out to production • Engineering Ops • Data orientation
  7. 35.

    @yonbergman DESIGN & ARCHITECTURE • Data Indexing • Best Practices

    • Design Docs & Reviews • Design Principals
  8. 36.

    @yonbergman WRITING QUALITY CODE • Code Reviews • Tech Debt

    • External Libs • Linting and Standards
  9. 51.

    @yonbergman POLYGLOT CHALLENGES • What tech does my group use?

    • What new piece of tech can I pick? • What do other groups use? • What did we stop using and why?
  10. 56.

    @yonbergman PILOT — Technologies in a limited pilot. It has

    not been decided yet if there should be wide adoption
 ADOPT — Technologies we feel strongly that we should be adopting this, and use it where appropriate.
 HOLD — Proceed with caution, as we are looking for alternatives, but no replacement is available yet.
 RETIRE — Technologies we need to actively replace at a reasonable pace balancing with new work.
  11. 58.

    @yonbergman Group A Group B Group C Go Pilot Adopt

    Java Adopt Javascript Adopt Adopt Adopt Ruby Hold Adopt Adop