GOTO Amsterdam 2016 Bas Peters @bas How people build software - - PowerPoint PPT Presentation

• GOTO Amsterdam 2016

Bas Peters @bas

Happiness

Developing the developers most important skill

♥

Bas Peters Solutions Engineer GitHub

Happiness

No mockery in this world ever sounds to me so hollow as that of being told to cultivate happiness. What does such advice mean? Happiness is not a potato, to be planted in mould, and tilled with manure.

Open Source Development

The development of open source software involves bringing a widely distributed group of people together to work on complex problems while primarily communicating online.

Open Source Development

The development of open source software involves bringing a widely distributed group of people together to work on complex problems while primarily communicating online.

• 2300% more requests served per second

• How people build software

Open source projects have constraints

• GEOGRAPHY

TIMEZONE CULTURE

• How people build software

Open source projects have constraints

• GEOGRAPHY

TIMEZONE CULTURE

• How people build software

Open source principles

TRANSPARENCYPARTICIPATION COLLABORATION

• How people build software

The medium and the message are transparent

• ELECTRONIC ASYNCHRONOUS LOCK-FREE

ARCHIVED

• How people build software

Minimizing friction enables participation

• DOCUMENTATION

README.md CONTRIBUTING.md

PULL REQUESTS

Make it easy to propose changes

AUTOMATION

Allows reviewers to focus on substance

• Minimizing friction - Documentation

• Minimizing friction - Pull Requests

• Minimizing friction - Pull Requests

Experimentation Without Risk

Branch — Question, Hypothesis, Experiment, Analyze, Conclude
 Pull Request — Gather feedback from peers and integrate with 3rd party products to perform automation for quality of code, build status, and deployment

• How people build software

Writing a Pull Request

• Include the purpose of this Pull Request
• Why the work is taking place
• Be explicit about what feedback you want
• Be explicit about when you want feedback
• @mention individuals that you want to involve in the discussion
• Remember that anyone in the company could be reading this Pull

Request

• How people build software

Providing feedback

• Familiarize yourself with the context of the issue and why this Pull

Request exists

• Explain your reasons why code should be changed
• Offer ways to simplify or improve code
• Aim to develop professional skills, group knowledge and product

quality, through group critique.

• Be humble, use positive language and use emoji to clarify tone 👎 ✨

✨

• How people build software

Responding to feedback

• Consider leading with an expression of appreciation
• Ask for clarification, offer clarification, explain the decisions you

made

• Try to respond to every comment
• Link to any follow up commits or Pull Requests
• Sometimes it can help to talk face-to-face

• Enabling participation

• Enabling participation

• Minimizing friction - Automation

• Apple Swift - Expanding Commit Access

• Minimizing friction - Automation

• Code deploys: bring operations to the developer

• Deploy master on merge

• Use branch based deployments

• Deployment status

• Haystack exception tracking

• Code refactoring with Scientist

• Code refactoring with Scientist

• How people build software

Put everyone in one spot with chat…

• Team rooms
• Region based rooms
• Social rooms
• Private chat
• Ops rooms

• … and bring your tools into your conversations

• Meet Hubot

• Hubot deploy example

• How people build software

Steps to create happy developers

• Ensure quality
• Implement rigorous testing and build
• Make deploys boring and predictable
• Require documentation in the

repositories

• Require mature and respectful

behavior

• Improve collaboration
• Let developers share their work
• Require public and focused code

reviews

• Give employees the confidence to

contribute code

• Put everyone in one spot with chat
• Share your experiences

• Thank you!