"Making It Better Without Making It Over"
summary
A nine‑year mobile job site begins with approximately zero JavaScript in 2008 and grows to 12,000 lines after adding Google Closure in 2013, increasing page load time and developer risk while still releasing features a few times a week. A simple bug exposes a function that takes 40 arguments, prompting migration to a page model and a single source of truth (Redux considered), plus guards: ESLint + package.json, NPM scripts, Jenkins hooks and Datadog instrumentation to catch regressions.
AI-written summary · about
chapters (10)
- 0:00Introduction and background
- 2:41The vintage mobile app
- 16:15The myth of rewrites
- 19:28Fixing the 40-argument bug
- 23:18Adding ESLint and standards
- 25:02Instrumenting key features
- 27:49Lessons from the past
- 31:00Teaching care and empathy
- 32:26The future of web tools
- 36:15Q&A and closing thoughts
related talks
24mMaking It Better Without Making It Over
18m50,000 lines of spaghetti code and how to unravel it
53mThe Unbearable Weight of Massive JavaScript
29mPreprocessors, Components, and CSS in JS or: How I Learned to Stop Worrying and Love the Website
29mDesigning very large JavaScript applications
45mDid We(b Development) Lose the Right Direction?
13mSpeed at Scale: Optimizing The Largest CX Platform Out There
58mKeep Betting On JavaScript