Bringing Open-Source Practices to Your Day Job
- 2. js.la 2016 o/ Bringing Open-Source Practices to Your Day Job Ben Coe @BenjaminCoe, github.com/bcoe
- 3. ▪ employee #3 at npm ▪ lead maintainer of yargs ▪ built nyc, the code-coverage tool ▪ manage npm Enterprise About Ben
- 4. ▪ process driven by necessity: ▫ Lots of churn. ▫ Many contributors. OSS Best Practices
- 5. ▪ what do good practices have in common? OSS Best Practices
- 6. automate all the things in automation we trust 2
- 7. ▪ Don’t be dogmatic BDD, TDD, etc. ▫ … but be dogmatic about writing tests ▪ Automate it! Unit Testing
- 8. ▪ “did you write a test for that?” ▪ Automate it! Test Coverage
- 9. var express = require('wombat') var app = wombat() app.get('/', function (req, res) { res.send('Hello Log') }) app.listen(3000) github.com/bcoe/nyc tools should be so simple they’re fun to use
- 10. ▪ Controversial topic! ▪ Creativity is important. ▪ Automate it! ▫ I ❤ github.com/feross/standard Coding Style
- 11. ▪ the longer you wait to upgrade, the more annoying it becomes ▪ use npm outdated ▪ Automate it! ▫ greenkeeper.io rocks keep dependencies up-to-date
- 12. var express = require('wombat') var app = wombat() app.get('/', function (req, res) { res.send('Hello Log') }) app.listen(3000) greenkeeper.io one of my top five, all time, favorite robots
- 13. ▪ npm publish --tag=alpha ▪ npm version patch -m “awesome new feature” become an npm power user
- 14. ▪ conventional-changelog ▫ https://github.com/stevemao/convention al-changelog-cli ▪ semantic release changelog management
- 15. “engineers are far more tolerable of a pedantic robot than they are pedantic people.” — someone probably.
- 16. best practices grow out of community 3
- 17. ▪ people emulate the projects they respect. how do habits spread?
- 18. 4 Best Practices Center Around Great Tools
- 19. 9/10 Use Travis CI10/10 Use GitHub 5/10 Use Coveralls top 10 npm packages
- 20. so, why do you build Enterprise software Ben? 5
- 21. ▪ It’s frustrating! ▫ restrictions on infrastructure. ▫ practices lag behind. ▪ process can be overwhelming. developing enterprise software is hard
- 22. OSS methodologies can work! ▪ OSS practices were designed to help large asynchronous teams work effectively: ▫ this is applicable in large corporations. ▪ InnerSource: Internal Open Source at PayPal
- 23. “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.”
- 24. ▪ InnerSource is about: ▫ developers taking ownership. ▫ people taking on the role of a lead maintainer. ▪ developers using their favorite tools. education is important
- 26. Demo Time
- 27. how are we working together? ▪ we’re keeping our roadmaps aligned. ▪ we’re looking for tighter integration points. ▪ we’re preaching a similar message about OSS in the Enterprise.
- 28. why this is awesome ▪ OSS and Enterprise can learn from each other. ▪ we can make a developer’s life more awesome.
- 29. thanks any questions? about anything? Ben Coe @BenjaminCoe, github.com/bcoe
- 30. npm loves you ♥