Google doesn't use something like SonarQube I guess. That's full of metrics like "fixed x bugs, improved code quality y%, reduced SQALE technical debt to z." I

Google doesn't use something like SonarQube I guess. That's full of metrics like "fixed x bugs, improved code quality y%, reduced SQALE technical debt to z." I can't say I blame author for leaving Google. So called "senior" devs who crank out garbage and then foist maintenance on lower level devs aren't people I want to work with either. They're going to keep you down as mid-level janitor until you get the stats to back your story up. Static code analysis can paint that picture quite nicely for management. Sadly, that didn't seem like an option at Google. If enough janitors leave, the whole place will stink soon. I think the author was wise to stand up for himself. Other Googlers who feel that way should join him.