> I don't care how you did it as long as it can be turned off with a feature toggle and does not break prod or introduce security vulnerabilities when I merge i

> I don't care how you did it as long as it can be turned off with a feature toggle and does not break prod or introduce security vulnerabilities when I merge it Does this not lead to poorly-written features that drag down future development yet cannot be turned off because they have grown important for the business? At least that's my experience with not regulating at least a basic level of code quality in the review. What are you doing differently to prevent that?