Lessons from 5 years of UI architecture at GitHub

on YouTube ↗31m

" summary

Five years of work on GitHub’s Rails monolith (5,000 models, 4,000 routes, 2,100 controllers, ~650 monthly contributors) yields concrete takeaways: adoption of React (≈250 React routes serving half of weekly pages) because web stacks can’t match mobile expectations, Primer and component drift create maintenance hell (5,000 buttons across the codebase), practical reuse of Highcharts and React Table saves time, design handoffs from Figma cause rework, and the rule of thumb is native is the new baseline and frontend costs 10x backend.

AI-written summary · about

" chapters (9)

1. 0:00Introduction
2. 2:18Three UI lessons at GitHub
3. 4:45Native UX baseline
4. 8:19App-like web pressure
5. 12:18Design system paradox
6. 17:38Front-end complexity
7. 23:11Design vs engineering
8. 27:44Budgeting UI complexity
9. 28:30Q&A

" related talks

• 25mLessons for frontend development at scaleHannes Obweger · LeadDev Berlin 2019
• 35mHabits for building a scalable UIYuval Bar Levi · code.talks 2022
• 40mHow I learned to love ReactDavid Mark Clements · Codemotion Rome 2016
• 19mPivoting to React, at scaleTilde Ann Thurium · JSConf Iceland 2016
• 39mBeyond ReactMarek Piasecki · The Rolling Scopes Conference 2018
• 26mFrontend At Scale - Experiences Using React In A Large OrganizationErik Wendel · ReactJS Day 2016
• 39mTomorrow's UI Architecture — Structuring UI applications Around FeaturesRob Fall · Rubyfuza 2018
• 22mDecomposition and beyond: frontend engineering at scaleNadia Makarevich · JS Kongress 2019