> do code reviews in order to make sure everyone understands the code. I like a hybrid "the person who wrote it can't deploy it" model. You get an informal cod

> do code reviews in order to make sure everyone understands the code. I like a hybrid "the person who wrote it can't deploy it" model. You get an informal code review and two sets of eyes/brains to the extent that the deploying engineer feels like they understand it enough to shepherd it into prod weighted against how important the component and the scope of the change is. It self scales from "copy change on the website yolo" to "this involves two new racks of servers and a database migration, I'm going to need to spend a week understanding it to the point I can make a plan."