@riamaria THIS. Managers tried this in the years of FORTRAN through some of the 1980s. It was ridiculous then and it still is now.
The value that a software provides is what matters: what it enables, how it empowers, how it was architected for future adaptations, and maintainability.
It's not white space utilization, number of CRs or LFs, font size, dropping braces or not, ternary IFs, large vs small commits etc.
Software is craftsmanship, not a robotic conveyor belt to KPI.