Lessons Learned While Building Hanami
summary
Hanami grows over four years from scratch to a production-ready framework now at 0.9 with a near-term 1.0 plan, replacing ActiveRecord with ROM for the model layer and recommending lighter local DBs like SQLite in guides to avoid onboarding friction. Lessons are concrete: write integration tests and fail-fast validations to avoid data- integrity bugs, remove global state to stop brittle builds, resolve naming trademarks early after the Lettuce/IBM confusion, and invest in docs and a code of conduct to seed contributors.
AI-written summary · about
chapters (14)
- 0:00Introduction and background
- 3:01Open source as a lonely job
- 6:54Don’t be attached to code or project
- 10:10Inspiration comes from solving real problems
- 13:24Progress over perfection and burnout
- 15:10Tragedy of the open source commons
- 17:00Avoid naming conflicts and legal issues
- 19:36People are the key to open source success
- 24:12First impressions and documentation matter
- 27:52Plant seeds for community growth
- 28:34Leadership through respect not authority
- 30:03Testing and data integrity in Ruby
- 33:20Global state and brittle tests
- 35:16Q&A: Global state and future plans
related talks
51m"A year with Hanami in production: the Good, the Bad and some Recipes"
01h 07mA year with Hanami in production: the Good, the Bad and some Recipes
42mHanami - New Ruby Web Framework
25mHanami - New Ruby Web Framework
23mHanami 2: New Framework, New You
36mReturn To Simplicity: Architect Hypermedia REST applications using Hanami + HTMX
53mKeynote: Refactoring Humpty Dumpty back together again
38mTaking Refinery off the Rails