Design Principles for Better FrontEnd Code
summary
Argues frontend JavaScript becomes maintainable by applying concrete rules: use === not ==, avoid var and prefer const/let with "use strict" or modules, and favor functional style plus SLAP (single level of abstraction). Demonstrates rewriting imperative code to functional then extracting isEven/double/add, runs Plato and sees maintainability metrics move from ~65% to ~93% and then 100%, uses ESLint to block bad patterns and runs Plato/ESLint (and Jest) in CI to fail builds below ~70–90%. Tools help but sometimes overstate quality.
AI-written summary · about
chapters (11)
- 0:00Introduction to front-end code quality
- 1:57Software design principles in JavaScript
- 7:56Avoiding JavaScript pitfalls
- 15:15JavaScript's legacy and quirks
- 27:15Functional vs imperative style
- 31:34Measuring code quality with tools
- 44:04Single level of abstraction principle
- 48:00Clean function parameters and structure
- 53:42Code reviews and team practices
- 56:31Unit tests and continuous improvement
- 1:00:26Q&A and closing remarks
related talks
38mGOOD CODE MYTHS
46mFunctional Frontend. Practical survival guide for backend engineers.
25mPrinciples for Scaling Frontend Application Development
29mLean Frontend Development
17mJS In The Enterprise - Lessons Learnt
25mDefault to Consistent
34m[Eng Sub]Is it Okay to Pursue Functional Programming on Frontend?
27mDesigning Even Larger (JavaScript) Applications