These might speak some to hiring, training, tooling, and team culture. First, one of these (blank lines) seem to be self correcting with a code style linter (n

These might speak some to hiring, training, tooling, and team culture. First, one of these (blank lines) seem to be self correcting with a code style linter (not linting creates PR noise, increases and reviewer and coding frustration). Second, blatant copy pasting should be difficult, as surely the context is different - thus descriptive names should often be renamed, and then at least some level of integration testing provides quick education to dry up code. And surely, if the team is reviewing, calling out repeated or obviously copied untested code, with no linting the developer would improve rapidly otherwise tire of the rework.