Цитаты из книги Robust Python: Write Clean and Maintainable Code

You need to be careful how you spend your time and effort.

I call it the “Ultimate Kitchen Assistant” (if you think this is a terrible name, you now know why I don’t work in marketing).

The greatest challenge in building a robust codebase is predicting the future.

The computer does exactly what you tell it to do (even if it’s not what you meant)

nobody wants a billing system that inherits from SplittableLunch

any developer who worked in the ’90s or ’00s probably remembers “Design Pattern Fever,” where you couldn’t walk 10 steps without running into an AbstractInterfaceFactorySingleton

You have one chance to get your interface right, but you won’t know it’s right until it’s used.

Usability testing is a great task for the more junior members on your team. Their curse of knowledge won’t be as strong as with the senior members, and they will be more likely to evaluate the design with a fresh set of eyes.

Once you get your types in front of users, those types will be used (and abused) in ways that you never thought of.

Surely every `if` statement is tested through unit tests to make sure they are consistent, right? Right?

Clean code matters.

Robust code matters.

A robust codebase is resilient and error-free in spite of constant change.