Building a Ruby Library the Parts No One Talks About
summary
Argues for concrete practices: follow semantic versioning and use a Gemfile with the pessimistic operator for dependencies; expose configuration as plain Ruby (a central configure block) rather than a DSL; prefer a namespaced logger like log4r over stdlib Logger; wrap errors in a single parent exception with descriptive subclasses (vagrant uses about 150 subclasses); add slow end-to-end acceptance tests (three hours) and run them before release; use Travis CI, keep README/docs with the code and generate API docs with yard.
AI-written summary · about
chapters (9)
- 0:00Start
- 3:09Configurable
- 11:39Workflow with Gemfile
- 19:09Central Configuration
- 20:13Instance Configuration
- 22:47Usage: Your API
- 26:23Bad: Result
- 27:16Single Parent Class
- 27:53Descriptive Subclasses
