This article seems to imply that yak shaving is better. I know it's not saying that explicitly, but having all functions implemented in an optimal way before shipping requires some measure of yak shaving.

I would rather capture the assumptions the code operates under, so that when one of the assumptions is violated, the build pipeline throws an error.