GitHub Flavored Ruby
summary
Five concrete practices used at GitHub defend against complexity: relentless modularization splits code into dozens of services like grit, smoke, burt rpc, chimneys and gollum so pieces can be open sourced and reused; Readme Driven Development means writing the README as a spec then moving implemented parts into the real README; rake gem provides copyable templates and rake tasks with no external deps for building and releasing gems; TomDoc documents method-level API and lands in rdoc 3.10; semantic versioning (major.minor.patch) prevents dependency hell.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 2:04Methodologies for Awesomeness
- 3:04Relentless Modularization
- 6:01GitHub Architecture & Open Source
- 11:01Readme-Driven Development
- 17:37Rake Gem for Packaging
- 23:59TomDoc Documentation
- 33:53Semantic Versioning
related talks
37mOpen Source Maintenance
27mFinding Beauty in the Mundane
30mA Documentation Talk
01h 12mRuby Best Practice Patterns
20mAutomating maintainers work: The Prototype
29mTaking over Someone Else's Open-Source Projects
31mTelling a Great Story on GitHub
39mMaintaining a big open source project: lessons learned
