Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Recap of Jordan DeaMattson TechTalk

Recap of Jordan DeaMattson TechTalk

Small recap from Jordan DeaMattson tech talk in Onebitmedia, Yogyakarta

Kuncara Adi Nugraha

April 29, 2015
Tweet

More Decks by Kuncara Adi Nugraha

Other Decks in Technology

Transcript

  1. Topics 1. Five Whys 2. Metrics and Analytics 3. Pick

    a Boring Tech 4. Devops as a culture
  2. Five Whys Simplest tool for root-cause analysis Useful for management

    roles Useful for postmortem / post-hoc explanations Pitfall: 1. Sometimes “how” is better 2. It might lead to blaming people
  3. Metrics / Data Driven Principles: 1. Assign owners 2. Create

    layered metrics, e.g: • Business metrics • Development metrics • Infrastructure metrics 3. Analyze and use for taking decision
  4. Pick a boring techs Innovations tokens concepts Boring ≠ Bad

    Boring means well-understood and lesser unknown situations / variables Credit: Dan McKinley
  5. Pick a boring techs (2) Redefine “best tool for the

    job” • Our job is “keep our company in business and make us still eat tomorrow” • Best tool is “keep problems as minimum as possible and solve requirement as maximum as possible” Credit: Dan McKinley
  6. Pick a boring techs (3) How to pick new techs?

    1. Let’s talk first 2. Can we solve with our current techs? 3. Addition or alternatives? Set clear expectations for migration Credit: Dan McKinley
  7. DevOps as Culture DevOps is not only tools Culture movement

    combined with development practices to enable rapid development