~/talk

Developer Productivity Engineering

on YouTube 11m
Talkat GORUCO 2017 · on Saturday, 2017-06-24· [devops-and-delivery, developer-experience]

speaker

name:Panayiotis Thomakos
links:none on file

resources

video:https://youtu.be/mL6kOPxuQTI
slides:none on file

summary

Applies Google SRE principles to developer productivity with a concrete DPE framework that identify measure prioritize and a checklist of six toil criteria for deciding what to automate. Measures combine surveys and instrumentation, and prioritization sums recurring toil cost, implementation and maintenance, and onboarding costs. A concrete result at Strava automates the mobile release workflow and converts ~20 developer hours per week into a net saving of 17 developer hours per week.

AI-written summary · about

chapters (12)

  1. 0:00Developer Productivity Engineering
  2. 0:41make others more productive
  3. 1:11challenging interesting
  4. 2:06framework
  5. 2:27site reliability
  6. 2:40identify measure prioritize
  7. 3:49manual
  8. 4:52scale linearly with growth
  9. 5:47repetitive automatable
  10. 7:29indirect approach
  11. 9:20onboarding cost how long before a new engineer can perform this task?
  12. 10:26Recording and Production Confreaks

related talks

~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.