James Brooks :: Working at Laravel
summary
Laravel LLC runs as eight engineers with no managers, 3,011 contributors to the framework, and about 305 million downloads (roughly four downloads a second). Collaboration uses GitHub, Basecamp with daily 4:00 check‑ins, Slack channels per product plus an emergency channel, Help Scout with hundreds of saved replies, Tuple for pair programming, Paint and GitHub CI. A Laravel Panel took 1.5 years to ship; Forge provisioning is rewritten to a single persistent SSH connection with atomic, unit‑testable provisioners and before/after/failed hooks.
AI-written summary · about
chapters (10)
- 0:00Laravel introduction
- 3:35Laravel’s growth
- 6:31Team structure
- 8:15Flat organization
- 10:21Remote collaboration tools
- 15:39Workflow optimizations
- 16:42Conventions and automation
- 18:27Pausing to refine
- 19:31Forge provisioning rewrite
- 23:32Q&A
related talks
28mCultivating success with Laravel
44mBuilding a complex product while scaling a team and a business on Laravel
41mAt the Heart of a Core Team
41mTwelve-Factor Apps
48mMigrating a 15 Year Old Enterprise Application to Laravel: Lessons Learned and Opportunities Gained
46mHow I Built and Scaled a SaaS Product Using Laravel
22mJemiah Sius at LeadDev West Coast 2023
01h 06mHow GitHub delivers GitHub using GitHub