Tales of Interest
summary
Stories focus on concrete failures and fixes: rspec moves from one maintainer to rspec core team grows from one to five and wrestles with encoding mismatches, Windows color output disappearing, and MRI quirks like MRI public_class_method leaks visibility on 1.9.3. CI realities bite — typical runs on MRI take 3–4 minutes but JRuby boot increases CI time from ~3–4min to ~50min so tests time out — and rubinius breaks when the stdlib becomes gems. Dogfooding surfaces swallowed exceptions and inspires tools like a custom formatter that skips integration tests when unit tests fail.
AI-written summary · about
chapters (4)
related talks
01h 00mTesting Heresies
37mRubinius - tales from the trenches of developing a ruby implementation
45mToward a Design for Ruby
42mThe Mechanics of Ruby
32mOnce Upon a Time, Ruby
52mStory Driven Development: The Next Generation of Rails Functional Testing
49mDeconstructing the hype: What people think is wrong with Ruby?
48mLightning Talks