- Forum Clout
- 4,903
Based.never, because while i'm sure that bitch dindu nothing on the project, every decent developer knows of lines of code is a retarded metric. Number of commits is maybe marginally better, but depending on your devops and infrastructure cadences you might have automated tools doing merges. If you use a certain type of delegated admin for IAM and CI/CD then your number of commits and merges will look very high. This is in lieu of service accounts. Basically you're using your own account , scoped down with (say SAML as an example) to do automated tasks.
This is why the whole "10x dev" trope is dumb as shit. Pushing a whole bunch of shitty commits that break builds, fail unit tests, or introduce bugs is actually worse than doing nothing at all. Using any of that as a KPI is retarded.
dont even think about calling me or this post autistic.
Some of the best developers only delete code.
At a lot of the best shops, it's not just commits and commit quality, it's how many eyeballs are on the user-facing screen that you added or modified.
And you also get metric bumps for deleting code that no one uses.
Dev life facts