I'd say 'Readability always comes first' - without readable code, maintenance and collaboration suffer; performance can often be optimized later.

In our team, we prioritized performance for a while and had to refactor later for readability; now I think a balance is ideal but it depends on the project's goals.

I'd pick 'Balancing both is key' - but what does that even mean in practice when deadlines are tight?

I'd say 'Readability always comes first' but only if the performance impact is negligible; can you share a scenario where prioritizing readability significantly affected performance?