On Second Acts
summary
Argues that Ruby is in a recognisable second act and needs engineers to embed into management to keep the hiring pipeline and diversity intact, not bleed off to Python; credits Rails’ real effect as changing business models and org structure — the “Rails as a Judo flip” that enabled fast full‑stack delivery. Recommends concrete tools and steps: version control, automated deploys, TDD and continuous delivery, and an apprentice model to hire and train juniors so the community actually grows.
AI-written summary · about
chapters (4)
related talks
27mSwitch Up: How to Switch Careers to Become a Ruby Engineer
30mThe How and Why of Ruby
06mRuby, the hidden programming teacher
10mMicrotalk: Working with Rubyists
40mCare and Feeding of Ruby Developers
46mClosing Keynote
22mJunior Gems: Hiring, Valuing, and Empowering the Next Wave of Ruby Developers
26mDon't Call It a Comeback
