Coordinate Ruby Teams With
summary
Chimes coordinates dozens of Ruby services by actually measuring them: a data pipeline parses 50+ Rails repos’ Gemfile Gemfile.lock gemspec Ruby version and Dockerfile to feed a live dashboard that shows over a thousand gems, how many point versions of Rails run in production, and which pins block upgrades. Policies become concrete — 90 days plus end of quarter — and dependabot minor updates move many repos forward. For PII the team builds a maskable value wrapper and a repo parsers and dashboard rollout with configurable strategies for logging or raising on unmasked access.
AI-written summary · about
chapters (9)
- 0:00Welcome
- 2:26iHeart Ruby team role
- 3:52Gem management challenges
- 8:42Gem dependency dashboard
- 11:54Introduction to masking personally identifiable information
- 15:30Maskable PII wrapper design
- 21:57PII masking rollout
- 24:52PII handling alternatives
- 26:00Q&A
related talks
29mMore Engineers, More Problems: Solutions for Big Teams
27mLaying the Cultural and Technical Foundation for Big Rails
09mRuby and Virtual Teams
38mThe Past, Present, and Future of Rails at GitHub
22mCreating a team mindset of continuous improvement
27mTaming the Kraken - How Operations enables developer productivity
28mUpgrading Rails: The Non-Technical Parts
34mShitlist-driven development and other tricks for working on large codebases