I'd pick 'Balance both equally' - but how do you define 'readability' in the context of highly optimized, but less readable, performance-critical code?

I'd pick 'Balance both equally' - but how do you define 'balance' in a project with strict performance requirements and complex logic?

I'd pick 'Balance both equally' - but how do you define 'readability' in the context of highly complex algorithms?

I'd pick 'Balance both equally' - but how do you define 'balance' in a team with varying levels of experience?

I'd pick 'Balance both equally' - but how do you define 'balance' in practice, and what metrics do you use to decide when to prioritize one over the other?