PHP UK Conference 2012: Scaling Communication via Continuous Integration
14 likes7,897 views
The document discusses the importance of developer culture and continuous deployment at Etsy, emphasizing the cultural elements that facilitate effective communication and integration processes. It highlights the need for clean code and tests, confidence in deployment practices, and strategies for improving developer happiness. Additionally, the document outlines approaches to managing test quality and streamlining coding standards within a constantly evolving engineering environment.
PHP UK Conference 2012: Scaling Communication via Continuous Integration
- 1. Scaling Communication via Continuous Integration Th e Fi n di ngs Th us Fa r!
- 3. LB Denker Anthropologist of Developer Culture @ Etsy
- 4. Anthropologist?!? ... only sort of ...
- 5. Methods of an Anthropologist Participant Observation Interviews Surveys
- 6. Developer Culture “The most important component of The Etsy Way is culture and that is as difficult to teach as it is important” — Chad Dickerson, CEO
- 7. Acquiring Culture “... humans acquire culture through the learning processes of enculturation and socialization ...”
- 8. Developer Culture “Always Be Pushing” Developer Happiness We trust people
- 9. “Anthropology demands the open-mindedness with which one must look and listen, record in astonishment and that which one would not have been able to guess.” — Margaret Mead
- 10. Deployinating All the Pushes One Button (stage) Logging Monitoring No Child Safety Locks
- 11. Anyone Can Deploy! Board Members Included
- 12. 20 Minutes or Less The Power of Continuous Deployment
- 13. Continuous What?!? Continuous... Unceremoniously... Initiated By... Apply Quality Integration Anyone Process Push New Code Deployment Anyone To Production Release New Delivery Product Feature
- 14. Communication Theory 1. The Basic Elements of Communication Source Destination Sender Message Channel Feedback Receiver 2. Goal-Oriented Communication
- 15. Goals “Always Be Pushing” You Shouldn’t Push on Red You Should Write Clean Tests You Should Write Clean Code Trust Everyone To Do The Right Thing
- 16. “Always Be Pushing” Instilling Confidence Th e Fi rs t In te r v ie ws
- 17. Confidence Continuous Deployment is... Scary A Safety Net Depends on Your Point of View
- 18. Branching was Too Costly
- 19. Always Ship Trunk Write Tools to Work with Trunk Do not Write Tools to Work with Branches Write Transparent Tools
- 20. Quality Process was Coupled to Pipeline
- 21. ‘Try’ Before You Commit Ability to Run Tests in CI Environment Actually Continuous Integration! Community Enforced! No Excuses!
- 22. Confidence Boost! The Impact of Knowing that Changes Pass the Tests Before Getting in the Pipeline
- 23. Why ‘Try’? No more clogging the pipeline CI in Pipeline was Final Sanity Check
- 24. Goal Achieved “Always Be Pushing”
- 25. You Should Not Push on Red De-Noising the Communication Channel Pa rt ic ip a n t Ob se r v ati on s over IRC
- 26. Where We Started From... Number of Total Time Flakiness Support Tests ~30 Practically Legacy Unknown ~50% Minutes None ~8 Platform ~1200 ~20% Small Core Minutes
- 27. A Bunch of Noise Need to Know How Much is Being Covered Need to Know What is Being Tested Need to Be Able to Detect Test Runner Errors Need to Have Actionable Test Results (Ownership)
- 28. De-Noise Number of Total Time Flakiness Support Tests ~30 Practically Legacy Unknown ~50% Minutes None >8 Platform >1200 ~5% Small Core Minutes
- 29. Goal Achieved You Should Not Push on Red
- 30. You Should Write Clean Tests Writing Simple Tests Isn’t Always So Simple Alter n ati ve Te ach ing Met h od s
- 31. How To Improve Test Quality Teach Them! But People Need to Want to Learn
- 32. Prove It! Number of Average Test Time Tests Time per Test Platform Tests 7:01 2332 0.18 seconds 0.00337 Unit Tests 0:10 2432 seconds DBUnit Tests 0:32 70 0.09 seconds December 2010
- 33. Test Classification PHPUnit @group PHPUnit XML Configuration + Some Pake Split By Point of Error ie. cache, database, network, sleep, time, etc. Flaky Test Silo
- 34. Goal Achieved You Should Write Clean Tests
- 35. Too Much To Read ... and to Communicate
- 36. How Do Communicate This? E-Mail? Nope! Wiki? Nope! Blog? Nope! Simplify Jenkins UI? YES!
- 37. Silent Green Taking a Chapter Out of xUnit Principles
- 38. Jenkins Plugins Master Project Plugin Triggering User Plugin Deployinator Plugin
- 39. You Should Write Clean Code Not Everyone Can Read (and Follow) a Coding Standard En a bl ing C ul tu re In fl ue n ce
- 40. Clean Code Start with Syntax Move to Style Then to Design Level
- 41. PHP Lint Run Locally Run on Pre-Commit Run on CI
- 42. Using CodeSniffer Draft Coding Style Guidelines Experiment With Various Sniffs Discover Actual Coding Syntax Tendencies Decide on Changes to Coding Style Guidelines Create a Strategy on How to Get to Green
- 43. Work in Progress You Should Write Clean Code
- 44. Getting to Green Send ‘Blame’ E-Mails Use a Staging Job in Try Do a Fix-It Competition
- 45. Trust Everyone To Do The Right Thing Balancing Enforcement with Freedom Fu tu re Wor k
- 46. Continuously Growing a Continuously Evolving Culture
- 47. More To Do Code Reviews, Second Pair of Eyes Entire Coding Standard in CI Mess Detector Standards PHPUnit --strict Standards PHPUnit Testing Standards ...
- 48. Developer Culture “Always Be Pushing” Developer Happiness We trust people
- 50. Company etsy.com About Our Craft codeascraft.com More From Me elblinkin.info
Editor's Notes
- #2: \n
- #3: \n
- #4: \n
- #5: \n
- #6: \n
- #7: \n
- #8: \n
- #9: \n
- #10: \n
- #11: \n
- #12: \n
- #13: \n
- #14: \n
- #15: \n
- #16: \n
- #17: \n
- #18: \n
- #19: \n
- #20: \n
- #21: \n
- #22: \n
- #23: \n
- #24: \n
- #25: \n
- #26: \n
- #27: \n
- #28: \n
- #29: \n
- #30: \n
- #31: \n
- #32: \n
- #33: \n
- #34: \n
- #35: \n
- #36: \n
- #37: \n
- #38: \n
- #39: \n
- #40: \n
- #41: \n
- #42: \n
- #43: \n
- #44: \n
- #45: \n
- #46: \n
- #47: \n
- #48: \n
- #49: \n
- #50: \n
- #51: \n
- #52: \n