Shipping with assertion turned on, should ideally be done from the projects’ inception and not when project is already being used by customers.

The point I’m trying to make is that if you and you’re team are still working on fast iteration cycles and aren’t there yet, you can slowly adapt to using asserts in production code, and not all at once.

Turning asserts on in production codebase is definitely a way to help team build fast iteration cycles in terms of Nth order effects.

They learn (or) you go belly up. You choose. It’s a do or die thing.

~ updated at: 2025-10-17T08:50:20.963Z