More Engineers, More Problems: Solutions for Big Teams
summary
Chime engineering triples in 18 months and tops about 600 engineers, which forces focus on tooling and process: an internal Rails app calculates nightly security grades and repository badges, sends Slack alerts, tracks A/B-or-better uptake and reduces audit work; approved Docker images get rebuilt to fix vulnerabilities; ActiveSupport::Notifications plus a LogSubscriber and parameter filtering provide reusable observability and safe logs; onboarding uses IRB, a question-game and mob programming to get hundreds of hires productive with Ruby and Rails.
AI-written summary · about
chapters (5)
- 0:00Introduction
- 5:17Proactive security culture
- 11:41Active Support observability
- 20:51Ruby onboarding games
- 28:18Summary
related talks
59mTech leadership, one year after
53mScaling Engineering by Hacking Conway's Law
30mThe Elements of Scaling
29mHacking Development Culture: Treating Developers As People
23mGad Salner- How to scale a unicorn-building engineering team (and stay sane)
28mFrom Startup to Scale Up: How to Scale Engineering teams
31mScaling Happy Engineering Teams
27mCoordinate Ruby Teams With