> The better way to think about it is that code review simply isn't optional. Of course it's optional. Tests are optional too. There are many projects and situ

> The better way to think about it is that code review simply isn't optional. Of course it's optional. Tests are optional too. There are many projects and situations where trading code quality for development speed makes sense. Especially when you're building MVP's, experimenting, or trying to validate market demand. It's also often not worth it on small to medium sized projects where only one person is working on the codebase (think 3-person project: designer, front-end dev, back-end dev). Larger projects with multiple people working on the same codebase are a completely different story. In those cases code reviews are valuable and highly recommended but still optional. The only thing that isn't optional is delivering a working product. Best practices == great, dogma == not great.