GOOD CODE MYTHS
summary
Argues that good code is defined by maintainability and safe, fast changes; recommends using TypeScript, linters and CI to make JavaScript maintainable and tests to allow safe evolution. Presents SOLID and Gang-of-Four patterns as pragmatic architectural guidance, and reports many production ML-era microservices (anti-spam, anti-fraud, search) where these practices kept development velocity roughly flat.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:33Good code myths
- 3:43Good code in any language?
- 6:13Good code as business
- 10:11Code reading
- 14:28Good vs bad code
- 16:36Good code and naming
- 18:45Tests as good code
- 20:29OOP in JavaScript?
- 24:30Design patterns pros/cons
- 27:52Prototypes and debt
- 30:45Think to write good code
- 31:50Q&A
related talks
01h 01mDesign Principles for Better FrontEnd Code
24mOne Hundred Years of JavaScript
34mNot Your Uncle’s Clean Code (TypeScript Edition)
26mModern Testing Practices in Frontend Applications
25mDefault to Consistent
17mJS In The Enterprise - Lessons Learnt
46mCompilers, User Interfaces & the Rest of Us
27mDesigning Even Larger (JavaScript) Applications