Techniques for writing high-quality code
summary
Concrete claims and tools: prioritize readable maintainable testable reusable code over clever one-liners, use IDE features (Rider, Visual Studio) plus linters and static analysis, apply dependency injection and small units for unit testing, and track metrics like bug frequency and rollback rate. Specific surprises: teams sometimes create one-solution-with-over-a-hundred-projects or misuse single-responsibility, and XML comments rot unless enforced. Technical debt is acceptable only when documented and scheduled for refactor on the Kanban.
AI-written summary · about
chapters (32)
- 0:00Introduction
- 1:37Highquality code looks different
- 5:33No comments
- 7:57Readability
- 11:10Type
- 13:42Style
- 16:35readable style
- 17:52HTML
- 18:41Navigation
- 19:40Clever code
- 20:54Clever code never is
- 21:44JavaScript
- 22:27Maintainable code
- 22:40readable code
- 22:52patterns
- 25:40organize your code
- 28:50First Break Down
- 29:47Refactoring
- 30:46Comments
- 33:19Classes
- 34:29Technical Debt
- 36:29Writing Tests
- 37:59Reusable Code
- 38:34Things to Consider
- 41:02Reusable
- 45:15Processes
- 46:18Code reviews
- 47:35Goals and metrics
- 48:33What customers get
- 49:54Perfect timing
- 50:08Questions
- 50:50XML Comments
related talks
25mBest Practices for Writing Clean and Maintainable Codes
28mSome small steps for code, One giant leap for quality
41mHow to write maintainable code
40mGood Code: What, Why, and How to Get There
33mBuilding Code Quality
51mReasons and Ways to Improve Code Quality
01h 00mBuilding Software Capital: How to write the highest quality code and why
45m'Writing code that lasts'...or writing code you won't hate tomorrow