Crowdsourced learning and Software Development as part of a Distributed Team
summary
A distributed volunteer group running daily scrums and frequent mob programming uses Ruby on Rails (plus EmberJS, Elixir, React, Ethereum experiments), Slack and c9 to onboard contributors; about 8,900 volunteers touch the org and 11 projects remain active. The team Dockerizes the main Rails site to avoid local dependency hell, then fixes real failures: missing Node/phantomjs installs, Docker volume hot‑reload, Windows CRLF line endings, and rack‑timeout errors (temporary 200,000,000 ms workaround). Capybara‑webkit dependency is removed when unused; result: Docker works for many but raises tradeoffs for local development.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:28Who am I?
- 3:38Talk Outline
- 5:44Agile approach
- 6:57Daily pair programming
- 8:31Software Development
- 11:25Meetings/pairing sessions recorded
- 22:23First pairing session
- 33:02Second PR
- 34:50Windows Issues
- 36:22Issues with volumes
- 37:34Docker Instance for Development
- 39:31Greater Rack Timeout Limit
- 40:03Pairing Sessions Derailed
- 40:53Removing capybara-webkit
related talks
09mRuby and Virtual Teams
34mShitlist-driven development and other tricks for working on large codebases- 34mShitlist-driven development and other tricks for working on large codebases
36mDistributed & Local: Getting the Best of Both Worlds
36mFrom massive pull requests to trunk-based development with Ruby
49mLearning through Osmosis
01h 33mLightning Talks
51mFrom the Trenches - Remote Scaled Trunk-Based Development