How do you find the balance between too much and too little in code and process reviews?

[00:00] There needs to be a little bit of like [00:01] we need to remove some croft in our [00:03] process. Some some of these checkpoints [00:06] these these meant well. We put these in [00:08] at a certain time. Maybe all these [00:10] checkpoints that we have are not as [00:12] valuable now as they were 5 years ago. [00:14] And maybe we need to call that back. Too [00:17] much bureaucracy in a workflow. And we [00:19] don't maybe don't want to call it [00:20] bureaucracy, but like all these little [00:21] things that we end up doing to like oh [00:23] we have to have multiple people review [00:24] these things. We need to have a PR [00:25] thing. and it's like this was a typo [00:27] different like how do you categorize [00:28] like if it still takes like an hour or [00:30] two to get a code change out like that [00:32] like it's it's a slow feedback loop and [00:34] so like deployments are slower than they [00:37] used to be we're spending a lot of time [00:38] waiting on everything to run like do we [00:40] were having the CIS run in our on GitHub [00:44] versus we used to run those on our [00:45] computers and our computers are actually [00:46] a lot faster than GitHub servers uh you [00:49] know and like we could probably run the [00:50] test suite locally and like trust each [00:53] other to do that there's some tension [00:54] there that I think we need they kind of [00:56] uh come to terms with as an industry.