O SlideShare utiliza cookies para otimizar a funcionalidade e o desempenho do site, assim como para apresentar publicidade mais relevante aos nossos usuários. Se você continuar a navegar o site, você aceita o uso de cookies. Leia nosso Contrato do Usuário e nossa Política de Privacidade.
O SlideShare utiliza cookies para otimizar a funcionalidade e o desempenho do site, assim como para apresentar publicidade mais relevante aos nossos usuários. Se você continuar a utilizar o site, você aceita o uso de cookies. Leia nossa Política de Privacidade e nosso Contrato do Usuário para obter mais detalhes.
▪ unit-testing is a great example:
▫ developers learned running large OSS
projects, the benefits of unit-testing.
▪ people emulate the projects they respect:
▫ this creates a feedback loop!
how do habits spread?
“What works best is studying the projects of
other maintainers already on this list,
interacting with the developers, learning
from them, and emulating their
▪ great indicator of quality.
▪ grew out of community
developers converge on the tools that
facilitate these practices
4 Best Practices
9/10 Use Travis CI10/10 Use GitHub 3/10 Use Coveralls
top 10 npm packages
▪ a pull request is opened on GitHub
▪ build kicks off on Travis:
▫ installing modules from public and private
▪ a conversation begins between developers.
the npm workflow
▪ pull-request kept up-to-date by robots:
▫ Coveralls reporting coverage.
▫ Travis CI reporting build status
▪ once merged, module is published to npm
▪ greenkeeper.io notifies other projects o/
the npm workflow
▪ tools work together elegantly.
▪ as many steps are automated as possible:
▫ let humans do what humans are good at.
▪ it feels (a little bit) like you command a robot
what makes this
enterprise software, a love story
so, why do you
▪ restrictions on infrastructure.
▪ practices lag behind.
▪ process can be overwhelming.
software is hard
▪ OSS practices were designed to help large
asynchronous teams work effectively:
▫ this is applicable in large corporations!
▪ InnerSource: Internal Open Source at PayPal
“The results were visible after 6 months. The
Checkout Platform team spends 0% of its
time rewriting code and just 10% reviewing
submissions. The team was able to do a
major refactoring and a 4x increase in
performance without planning for it. The
mindset moved from blocking change to
mentoring and coaching.”
▪ InnerSource is about:
▫ developers taking ownership of repos.
▫ people taking on the role of a lead
▪ developers need tools that empower them.
education is important
▪ good developer tools do more than deliver
an asset to a build server:
▫ there’s a real disconnect between devs
and ops folks here.
what are good
▪ it’s about facilitating communication.
▪ it’s about discovery.
▪ it’s about automation.
▪ it’s about delivering an asset to a build
what do I mean by