Mostly agree, but "done over perfect" is worth being careful with. In my experience junior developers hear that and use it to justify shipping things that are not actually done — they are just finished enough to close the ticket. The senior version of that principle is closer to: know precisely which corners you are cutting and why, and make sure the team knows too. Cutting corners invisibly is how you accumulate the kind of technical debt that nobody can explain when you try to fix it two years later.