Developer Joy - How great teams get s%*t done
•
0 likes•339 views
Join Sven and learn how great software teams measure and improve their developer experience, coordinate work across teams, run autonomous but highly aligned teams, and create a healthy and joyful engineering culture. Always backed up by data (not driven) instead of opinions. The talk will demonstrate how great teams faced development challenges, reinvented themselves, and created new ways of working to get s%*t done. Without losing sight of what makes this craft fun for engineers.
Recommended
More Related Content
Similar to Developer Joy - How great teams get s%*t done
Similar to Developer Joy - How great teams get s%*t done (20)
More from Sven Peters
More from Sven Peters (20)
Recently uploaded
Recently uploaded (20)
Developer Joy - How great teams get s%*t done
- 1. DEVELOPER How great teams get s%*t done @svenpet Sven Peters DevOps Advocate JOY
- 3. The Cloud Container Microservices Security & Governance You build it, you run it.
- 10. Bethlehem Steel
- 11. 400% increase Workers only doing repetitive task Productivity New roles Managers doing the thinking
- 12. years ago 125
- 14. Developer 10% more story points 20% faster pull request reviews Thank you Taylor
- 17. BACK< DevJ to oy
- 21. TECHNICAL DEBT
- 22. of dev time used for 10% of dev teams manage 42% TECHNICAL DEBT
- 23. of dev time used for 10% of dev teams manage 42% TECHNICAL DEBT
- 24. It all starts out nicely package com.miguelcatalan.materialsearchview; import android.app.Activity; import android.widget.ListView; import android.widget.RelativeLayout; import android.widget.TextView; import java.lang.re fl ect.Field; import java.util.List; /** * @author Sven Peters */ public class MaterialSearchView extends FrameLayout implements Filter.FilterListener { private MenuItem mMenuItem; private boolean mIsSearchOpen = false; public MaterialSearchView(Context context) { this(context, null); } public MaterialSearchView(Context context, AttributeSet attrs) { this(context, attrs, 0); @Override public void onTextChanged(CharSequence s, int start, int before, int count) { mUserQuery = s; startFilter(s); MaterialSearchView.this.onTextChanged(s); } }
- 25. It all starts out nicely /** * Return true if search is open * * @return */ public boolean isSearchOpen() { return mIsSearchOpen; } /** * Open Search View. This will animate the showing of the view. */ public void showSearch() { showSearch(true); } /** * Open Search View. if animate is true, Animate the showing of the view. * * @param animate */ public void showSearch(boolean animate) { if (isSearchOpen()) { return; } //Request Focus mSearchSrcTextView.setText(null); mSearchSrcTextView.requestFocus(); if (animate) { AnimationUtil.fadeInView(mSearchLayout, AnimationUtil.ANIMATION_DURATION_MEDIUM @Override public boolean onAnimationStart(View view) { return false; }
- 26. /** * Return true if search is open * * @return */ public boolean isSearchOpen() { return mIsSearchOpen; } /** * Open Search View. This will animate the showing of the view. */ public void showSearch() { showSearch(true); } /** * Open Search View. if animate is true, Animate the showing of the view. * * @param animate */ public void showSearch(boolean animate) { if (isSearchOpen()) { return; } //Request Focus mSearchSrcTextView.setText(null); mSearchSrcTextView.requestFocus(); if (animate) { AnimationUtil.fadeInView(mSearchLayout, AnimationUtil.ANIMATION_DURATION_MEDIUM @Override public boolean onAnimationStart(View view) { return false; } Sometimes it ends in a mess }
- 27. Your coding guidelines caught this.
- 28. Your coding guidelines caught this, right?
- 29. Team
- 30. Class names Are CamelCase Prefix private variables with underscore Private variables Single Responsibility Principal A class should have one and only one job Don’t assemble String with + Use either .format or % instead No line longer than 120 characters Line length Don’t use line continuations Break up long lines using parentheses () No Tabs 4 spaces are for indention Are lowercase. The can contain underscores Variables and function name Python Coding Guidelines
- 32. You’re doing code reviews, right?
- 33. export default function DateTimeSlider({ onChangeCallback, timeZone, time_min, time_max, autoUpdateSlider }: DateTimeSliderProps) { const [timeWindow, setTimeWindow] = React.useState<number>(30 * 60) const [value, setValue] = React.useState<number[]>( [time_min, time_min + timeWindow], ); const handleSliderChange = useCallback(( event: Event, newValue: number | number[], activeThumb: number) => { if (!Array.isArray(newValue)) { return; } + var counter = 5; + var factorial = 1; + while (counter > 1) + factorial *= counter—; + const clamped = Math.min(newValue[0], time_max - timeWindow); + setValue([clamped, clamped + timeWindow]); + } }, [timeWindow, time_min, time_max]); const throttledValue = useThrottle<number[]>(value, 200) WTF @sven?
- 34. export default function DateTimeSlider({ onChangeCallback, timeZone, time_min, time_max, autoUpdateSlider }: DateTimeSliderProps) { const [timeWindow, setTimeWindow] = React.useState<number>(30 * 60) const [value, setValue] = React.useState<number[]>( [time_min, time_min + timeWindow], ); const handleSliderChange = useCallback(( event: Event, newValue: number | number[], activeThumb: number) => { if (!Array.isArray(newValue)) { return; } + var counter = 5; + var factorial = 1; + while (counter > 1) + factorial *= counter—; + const clamped = Math.min(newValue[0], time_max - timeWindow); + setValue([clamped, clamped + timeWindow]); + } }, [timeWindow, time_min, time_max]); const throttledValue = useThrottle<number[]>(value, 200) This code is ugly
- 35. export default function DateTimeSlider({ onChangeCallback, timeZone, time_min, time_max, autoUpdateSlider }: DateTimeSliderProps) { const [timeWindow, setTimeWindow] = React.useState<number>(30 * 60) const [value, setValue] = React.useState<number[]>( [time_min, time_min + timeWindow], ); const handleSliderChange = useCallback(( event: Event, newValue: number | number[], activeThumb: number) => { if (!Array.isArray(newValue)) { return; } + var counter = 5; + var factorial = 1; + while (counter > 1) + factorial *= counter—; + const clamped = Math.min(newValue[0], time_max - timeWindow); + setValue([clamped, clamped + timeWindow]); + } }, [timeWindow, time_min, time_max]); const throttledValue = useThrottle<number[]>(value, 200) It would be nicer if you’d use a for loop
- 36. Don’t be a jerk.
- 37. Who has been bullied by a jerk?
- 38. Jerks are the reason people hate code reviews.
- 39. Team
- 40. Reviewer Author ASSUME COMPETENCE EXPLAIN REASONING BE CONSTRUCTIVE
- 43. Team
- 44. Test
- 45. Test
- 47. Build & Test TEST FAILED Re-run Test TEST PASSES Create PR .skip test Add comment to PR Flaky Test Detector Flaky Test FlakeOff Houston, we have a flaky test
- 49. Dev Flow Code
- 50. Dev Flow Code Build & Test Deploy hours to minutes minutes to seconds
- 51. Review Dev Flow Code Build & Test Deploy hours to minutes minutes to seconds Review days
- 52. Team
- 53. 3 days average from opening to merge a pull request
- 54. 3 days working on something else and go back.
- 55. Open Pull Request Fixing height of the screen Open Pull Request Adding user setting functionality Open Pull Request Optimising performance for chrome @alice @tom @alice @tanja @mark Puneet Arora Team lead
- 56. Open Pull Request Fixing height of the screen Open Pull Request Adding user setting functionality Open Pull Request Optimising performance for chrome @alice @tom @alice @tanja @mark Puneet Bot
- 59. Flow
- 60. Traffic Flow: 191 (vehicles per minute)
- 64. Autonomous Teams Feature A Platform Feature C Feature B Testing
- 65. Autonomous Teams Highly Aligned Designer Tester Ops Developer
- 66. Autonomous Teams Highly Aligned Designer Tester Ops Developer Developer Developer Developer
- 67. Team
- 68. Devs Exploratory Test Automated Test A Q
- 69. Devs Exploratory Test Automated Test A Q 🍹
- 72. Test Automation Platform Software Engineer on Test
- 77. Team
- 78. Make Create
- 82. Goals, Signals, Measures Demos Prototypes Project kick off Wonder Explore Make Impact
- 83. Demos
- 84. DEMO OPEN Everyone can join OUTCOME Show customer value CELEBRATE Recognise great work GROUP THINKING Challenge the solution SESSION
- 87. If you can’t measure it, you can’t improve it. Peter Drucker
- 88. Time To Restore Change Failure Rate Start with DORA Lead time for changes Deployment Frequency
- 89. Ticket Cycle Time From idea to deployment How often do we deploy code to production Deployment Frequency Wait Time Total of build time, deploy time, etc.. Keeping the lights on Time spend on bugs, infra, etc. Ratio between successful and failed deploys Change Failure Rate Bug resolutions Critical bugs fixed Incident Response Time How fast are we reacting? What’s the time to bring a service up again Time to Restore Important for the team?
- 90. Ask your developers Measurements & Baselines
- 91. The Wallboard
- 94. Ask your developers CheckOps
- 95. GitHub Good Day Project M T T W F M T T W F Activities / day How good was your day?
- 96. Review Deploy Idea Code 3 days 1 day 3 days 2 days 12 days Plan
- 97. Software development is not a production line
- 98. Measure what is important, don’t make important what you can measure. Robert McNamara
- 99. Measure & Baseline Ask your developers
- 100. Measuring Developer Joy Speed to ship quality code Waiting time Execution independence Access to tools, processes, and practices Effort managing external standards Managing code, pipeline, infrastructure Ramp up time Developer satisfaction
- 101. Measuring Developer Joy Speed to ship quality code Waiting time Execution independence Access to tools, processes, and practices Effort managing external standards Managing code, pipeline, infrastructure Ramp up time Developer satisfaction
- 102. Measuring Developer Joy Speed to ship quality code Waiting time Execution independence Access to tools, processes, and practices Effort managing external standards Managing code, pipeline, infrastructure Ramp up time Developer satisfaction
- 103. Measuring Developer Joy Speed to ship quality code Waiting time Execution independence Access to tools, processes, and practices Effort managing external standards Managing code, pipeline, infrastructure Ramp up time Developer satisfaction
- 104. Measuring Developer Joy Speed to ship quality code Waiting time Execution independence Access to tools, processes, and practices Effort managing external standards Managing code, pipeline, infrastructure Ramp up time Developer satisfaction
- 105. Measuring Developer Joy Speed to ship quality code Waiting time Execution independence Access to tools, processes, and practices Effort managing external standards Managing code, pipeline, infrastructure Ramp up time Developer satisfaction
- 106. Measuring Developer Joy Speed to ship quality code Waiting time Execution independence Access to tools, processes, and practices Effort managing external standards Managing code, pipeline, infrastructure Ramp up time Developer satisfaction
- 107. Measuring Developer Joy Speed to ship quality code Waiting time Execution independence Access to tools, processes, and practices Effort managing external standards Managing code, pipeline, infrastructure Ramp up time Developer satisfaction
- 108. Measuring Developer Joy Speed to ship quality code Waiting time Execution independence Access to tools, processes, and practices Effort managing external standards Managing code, pipeline, infrastructure Ramp up time Developer satisfaction
- 109. Measuring Developer Joy Speed to ship quality code Waiting time Execution independence Access to tools, processes, and practices Effort managing external standards Managing code, pipeline, infrastructure Ramp up time Developer satisfaction
- 110. Speed to ship quality code Waiting time Execution independence Access to tools, processes, and practices Effort managing external standards Managing code, pipeline, infrastructure Ramp up time Developer satisfaction Satisfaction
- 111. Speed to ship quality code Waiting time Execution independence Access to tools, processes, and practices Effort managing external standards Managing code, pipeline, infrastructure Ramp up time Developer satisfaction Importance Satisfaction
- 112. Satisfaction Importance Ramp up time Wait time Speed to ship Managing code, tools , pipelines Access to tools Execution independence Managing external standards Developer satisfaction
- 113. How is your DEVELOPER JOY bit.ly/developerjoy ?
- 114. Try to fix things DevEx hack 20% time DevJoy week Include in sprint
- 119. AUTONOMOUS TEAMS
- 124. Thank you DEVELOPER Don’t forget to have fun. JOY