Download to read offline
Uploaded byRoy Braam
Happy Developers write better code
The document discusses the importance of creating a positive developer experience (DX) to enhance productivity and job satisfaction for developers. Key factors include efficient onboarding, appropriate tools, collaborative teamwork, and supporting automation to reduce repetitive tasks. Ultimately, happy developers produce better code and contribute to a more effective development environment.
Happy Developers write better code
- 1.
- 3. WHAT MAKES YOU AHAPPY DEVELOPER? Mentimeter URL + code
- 4. • Roy Braam •Director OpenValue Amsterdam • Developer / Architect @rbraam #happydeveloper
- 5.
- 8. DEVELOPERS, DEVELOPERS, DEVELOPERS, DEVELOPERS,DEVELOPERS, DEVELOPERS And the experience while developing software
- 9.
- 10.
- 11. GOOD DEVELOPER EXPERIENCEIS ABOUT CREATING AN ENVIRONMENT IN WHICH A DEVELOPER CAN DO THEIR BEST WORK
- 12. UX & DX •Developers are users • DX to developers is as UX to users • Shared principles • DX & UX important for same reasons.
- 13.
- 14. MORE…. • Environment • Processes •Team chemistry • Tools • Libraries • API’s • Infrastructure • …
- 15. A GOOD DEVELOPER EXPERIENCEIS UNDERVALUED
- 17.
- 18. “DEVELOPERS CAN JUST FIGURE IT OUT,AND USE WHATEVER THEY WANT” And we call it DevOps….
- 19.
- 20.
- 21. WHY IS GOODDEVELOPER EXPERIENCE IMPORTANT?
- 22.
- 23.
- 24. RESULTS OF GOODDX • Efficient • Motivated • Shorter time to market • More focussed • Less duplicates and overhead • Sense of ownership • Working together • Working with the right tools • Feedback loops are short • Goal • Productivity increases • Likely to stay longer.
- 25.
- 26.
- 27.
- 28. INTERVIEW • Matching withwork • Be aware what you ask • Give proper feedback • Works both ways.
- 29. INTERVIEW - HOW •Team involvement • Review Pull-request • Code together • Focus on what is known.
- 30.
- 31. ONBOARDING • One ofthe first touchpoints • A “magic” moment • Social & Technical • Bad onboarding make people leave • Being productive makes developers happy.
- 32. ONBOARDING - HOW •Pair / Mob • Buddy • Documentation • Onboarding tasks • Provide context • Team lunch • …
- 33.
- 34.
- 35. FITTING ARCHITECTURE • OverSimplified - extra work later • Over Complex - extra work now • Architecture is not only for architects.
- 36.
- 37. AUTOMATE • Where possible •Developers are want to be lazy • Repetitive work is demotivating • Fix it once, love it many.
- 38. AUTOMATE • Sooner thebetter • Step by step • Share local automation.
- 39. BUILD PIPELINE THATTAKES 3 HOURS IS NOT GOOD DEVELOPER EXPERIENCE
- 40.
- 41. WAY OF WORKINGTHAT SUPPORTS DEVELOPMENT • SAFe, Agile, Scrum, DSDM, RAD, XP, AUP, LeSS, RUP • Deployment • Feedback/reflection • From idea to production • Focus time.
- 42.
- 43. PROVIDE RIGHT TOOLING •Local system • CI/CD pipelines, Testing Frameworks, Monitoring, Observability, (Aggregated)Logging • Should be coherent • Might be opinionated • Leave room for deviation.
- 44. TOOLING • Need tobuild your own platform? • Boilerplate project • Setup by Self-service
- 45.
- 46. POWER TO THETEAMS • Be able to do their work • Trust • Power - Responsibility • DevOps!?.
- 47.
- 48. DOCUMENTATION • Difficult • Documentationshould answer questions • Point to documentation • Up to date.
- 49. DOCUMENTATION • Make itfindable • Choose the location • Generate where possible.
- 50.
- 51. WORK AS ATEAM • Team instead of individuals • Safe environment to develop • OK to fail culture • Help each other.
- 52. WORK AS ATEAM • Pair/Mob • Agree on ”stuck-time” • Focus on getting it done • Communicate.
- 53.
- 54. EMPATHY • Try tounderstand the pain • Be the user/developer • Eat your own Dog Food • Fix things for others.
- 55.
- 56. AVOID BLOCKING DEPENDENCIES •Outside the team • Between teams • Self-service • Work together.
- 57.
- 58. KNOWLEDGE SHARING • Supportsgrowth and innovation • We instead of Them • Helps to collaborate • Fun.
- 59. KNOWLEDGE SHARING • Opendiscussions • Communities • Presentations • Mini-conferences • Guest speakers.
- 60. SUMMARY • Interview •Onboarding • Fitting architecture • Automate • Way of working that supports development • Provide the right tooling • Power to the teams • Documentation • Work as a team • Empathy • Avoid blocking dependencies • Knowledge sharing
- 61.
- 62.
- 63.
- 64. Happy developers write bettercode Roy Braam @rbraam #happydeveloper
- 65.