Earlier quoted context omitted.
> Hiring bad people in engineering can cripple your services. Adding code that's hard to understand, has poor time complexity, or is over-engineered can add more technical debt that any one feature is solving for, and reworking that code can cost way more time than it originally took to write once it's part of some production service. So use code reviews prior to merging, and prevent that code from becoming part of t…
The last place I worked, the junior engineers reviewed the interns code. There weren't enough senior engineers to review the junior engineers code, so we ended up reviewing each other's code. I was pretty green at the time, so we just ended up with a terrible codebase after being there for a few years. It was already bad to begin with, but that's because it seemed like what that company does is churn through junior e…
If your linter already complains about bad indentation, your senior devs can concentrate their limited time on more substantive issues.
Of course, that scaling by technology has limits.