Michael Bernstein of Code Climate explains how to monitor your code's quality with static analysis. He tells us how you can maintain or improve quality over time, and what you can do to fix poor code.

Here's what to listen for:

• 00:44 What is high quality code?
• 02:06 What is code that’s easy to read?
• 04:12 What is overly clever code?
• 06:44 What is the danger of overly clever code?
• 07:30 Is code able to document itself?
• 09:47 When do developers read code?
• 10:40 Why do people spend more time reading code than writing it?
• 12:42 What are some common qualities that make for lower-quality code?
• 15:09 What is a test?
• 16:50 What is modular code?
• 17:57 What is unmodular code?
• 18:37 What is static analysis?
• 20:56 What does a static analysis tool do?
• 21:34 What do I do when I receive a poor Code Climate score?
• 24:25 How do I prioritize changes to my codebase?
• 29:59 What are hot spots in Code Climate?
• 32:07 What does Code Climate’s test coverage feature do?
• 33:45 How do you determine how good your tests are?
• 34:51 What is a good unit test?
• 37:09 What is mob refactoring?
• 37:43 Can you do mob refactoring remotely?