[tyre]

Huge disagree, as a manager. It depends on the thing, of course. If you're rushing into a giant re-architecture by Tuesday, that's dumb. If you have some change you want to make, go for it.

My default is to trust engineers based on my experience with and expectations for them. If they want input—anything from a deep review to a gut check—I'm happy to help. If you're looking for a gut check, this is a fine way to do it. It communicates your level of confidence, which is an important data point for me.

If someone is adding a GH action, do we need a prototype? Maybe! But also maybe not. Bias towards action. Not YOLOing, not hacked together crap, not vibe code merged without review. But I've found that great engineers are often more hamstrung by permission checks than the issues they're meant to prevent.