Good Code
summary
Two clear practices decide whether code stays readable and maintainable: document and enforce style decisions — pick rules up front, put them in the repo README, wire up eslint/prettier/typescript and CI checks — and always explain unusual decisions in code comments — show why a regex parses "min..max", why a third‑party modal fires onClose twice and is debounced, or why an Android workaround exists. These two actions reduce surprises, speed onboarding, and prevent future rework.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 3:24Code quality in consultancies
- 9:50Bad code causes
- 13:19Consistency in JavaScript
- 17:56Zen of codebase
- 18:40Two tips for better code
- 25:00Summary & Q&A
