Microtalk: Working with Rubyists
summary
Claims that management can stay technical and that still writes code while leading a team, with concrete proof of being top contributor to the main monorail application. Describes hiring and feedback practices: formal reviews twice a year, constant peer feedback, written team creeds, and trusting people to fail fast. Emphasizes Ruby culture priorities — testing, beautiful code, new libraries — and that people problems outsize concurrency or GC as the hardest engineering challenge.
AI-written summary · about
chapters (8)
- 0:00Intro
- 0:34I'VE BECOME A MANAGER
- 1:38NEVER PERFECT ALWAYS DIFFERENT PROBLEMS
- 4:58TREAT PEOPLE LIKE ADULTS Pay them in trust let them pay you in quality code
- 5:32GIVE AND SOLICIT FEEDBACK Positive and Negative
- 6:15ALWAYS BE WILLING TO SHARE KNOWLEDGE Mentoring is a way of life
- 6:58SET OUT WITH IDEALS AND LIVE BY THEM The Need for Creeds
- 7:40ADMIT WHEN YOU'RE WRONG, LEARN FROM IT I'm wrong a lot. Learn from other people's
