How to become a better software engineer by breaking things

How to become a better software engineer by breaking things

Menschen machen Fehler und wo viele Menschen zusammenkommen (Spoiler: in Unternehmen), kommt es auch zu vielen Fehlern. Aber anstatt sie zu verurteilen, sollten wir Fehler nutzen und als Chance verstehen, etwas zu lernen. Dazu gehören nicht nur Software-Lösungen und Tools, sondern vor allem der Rückhalt der gesamten Firma bzw. der Kollegen. Der Talk wird dir Einblicke geben, was wir bei sipgate schon kaputt gemacht haben und wie wir daraus lernen konnten.

3a15b4f5e737fed2ecab7b16c84aff1b?s=128

Benjamin Kluck

February 05, 2020
Tweet

Transcript

  1. 1.

    Benjamin Kluck & Peter Mösenthin: Creating a safe to environment

    How to become a better software engineer by breaking things #HBABSE Part 2 .fail..
  2. 3.

    180 Employees 600 kg Coffee 2019 Deployments / Day Ø

    100 300 Server »hubot party bis 02:00« Chatbot command #1 1300 Post-Its / Tag 445 VMs 6.600.000 API requests / Day Düsseldorf 120 Services
  3. 11.

    Failure Culture ➡ “Failing is OK” ➡ “I trust that

    you do your best!” ➡ “Do or do not, there is no try”
  4. 12.

    Blame Culture ➡ “Don’t fail!” ➡ “It’s better to keep

    doing things the same way!” ➡ “Never change a running system!” ➡ “It wasn’t me!”
  5. 13.
  6. 14.
  7. 15.

    Bias for Action “Speed matters in business. Many decisions and

    actions are reversible and do not need extensive study. We value calculated risk taking.” https://www.amazon.jobs/en/principles
  8. 16.

    Fail fast, fail often “By failing early, you can create

    something useful and deliver it to the consumer as soon as possible.” Many people (including Martin Fowler)
  9. 24.

    .Feedback talks. .Non violent!. .Descriptive!. .Non judging!. .Stay positive!. .Highlights.

    .Ideas. .Keeps. .Bad stuff. .No defensiveness!. .Ask questions!. .What’s done is done..
  10. 26.
  11. 27.

    Learning methods Conferences YouTube etc. (also conferences) Books! (The paper

    thingies) Microdegrees Knowledge exchange Meetups ...
  12. 34.
  13. 36.
  14. 37.
  15. 39.

    “Canary deployments are a pattern for rolling out releases to

    a subset of users or servers” – Ben & Peter, 2 seconds ago
  16. 40.
  17. 45.
  18. 55.
  19. 57.
  20. 60.
  21. 61.
  22. 65.
  23. 66.
  24. 68.

    Benjamin Kluck & Peter Mösenthin: Creating a safe to environment

    How to become a better software engineer by breaking things #HBABSE Part 2 .fail..