Getting called up to the Majors
summary
Shifts from solo Heroku apps to a giant Rails app with a complicated data model and a CI test suite that took an hour, learns to survive and contribute in a legacy codebase touched by 30+ people, embraces pairing culture including 100% pairing plus ping‑pong and extreme pairing, practices specific tools and migrations like Rails 3.2, Jenkins then Travis, MySQL and EC2 where a weekend Minecraft experiment becomes a rebuilt CI server, and moves into Backbone after a six month review.
AI-written summary · about
chapters (6)
- 0:00Start
- 4:24Moving to San Francisco
- 9:33Maven Link
- 12:15The Dev Stack
- 17:09Extreme Pairing
- 22:19Asking Questions
related talks
27mSwitch Up: How to Switch Careers to Become a Ruby Engineer
52mNew dev, old codebase: A series of mentorship stories
26mHow to be an Awesome Junior Developer
26mLet the Junior Dev Upgrade Rails
28mBreaking Rules to Ship Products: A Beginner's Rails Journey
34mBuilding a Culture of Learning
39mNew Dev, Old Codebase: A Series of Mentorship Stories
22mIt Takes a Village to Make a Programmer