Knowing Your TCO (Total Cost of Ownership)
summary
Argues that cutting dependencies uncovers hidden liabilities beneath node_modules and reduces supply chain risk illustrated by left-pad and event-stream breakages; recommends treating developer experience as a spectrum rather than defaulting to frameworks, using the browser and MDN plus tooling like Mocha and ESLint and projects such as Greenwood.js; reports measurable developer feedback lag from TypeScript compiles, claims fewer tools give faster refreshes, easier maintenance, and workable upscaling paths.
AI-written summary · about
chapters (5)
- 0:00Start
- 0:52Setting Sail
- 8:01The Inverse Iceberg
- 15:47Technical Accounting
- 22:48The Spectrum of Developer Experience
related talks
49mFront Ends for Back End Developers
05mDo More with Less
18mJavaScript tooling has a blind spot: codebase-wide questions
06mLightning talk from Andrey Sitnik
56mComponents and Modules
24mDrawing the line between 3rd party and custom code
46mFrontend Minimalism in Action: Do More With Less JavaScript
39mWhat Can We Learn With JavaScript Fatigue?
