Clean code is the most essential part of building great software with your team. In this interview Uncle Bob shares half a century worth of experience and practical tips about measuring code quality, leading your team, having them write clean code, and selling clean code standards to impatient clients.
In this interview we're covering:
- Definition of clean code
- Metrics of clean code
- Consequences of bad code
- Tips for engineering managers
- Communication tips
- On-boarding to clean code
- Scaling with clean code
- Clean code vs deadlines
- And more!
Excerpt from the interview:
"The underlying theme is that if you want to go fast, meet schedules, and keep your customers and your managers happy, keep your code as clean as possible. Nothing will make you work faster than keeping your workspace clean.
One of the most important things a developer can say to a manager is the word no. You must be able to look your manager in the eye with all the empathy and sympathy you can muster, and say, “The answer is no.” You will save a lot of money if you say no at the right time.
Never promise to do something you know you can't do. They will believe you, bet a lot on your ability to do it, and you will let them down."
Click here to read the full interview!
