|
|
|
|
|
by coyotespike
1307 days ago
|
|
I completely agree. In fact, even just for specifically code-related work, think about code review. Really closely reviewing a big PR can take hours. Here's a fun thought experiment. How many engineers in a team do you need before one of them could be employed full-time just reviewing others' code? I don't know the answer, but it could be as few as 10 other team members, depending on the size and complexity of the PRs. And reviewing code is extraordinarily productive - looking for correctness, code style and patterns, tool selection and usage, app structure, etc., etc. One of the best ways to mentor team members and help keep the codebase clean. |
|