> A "engineering manager" should have at least one task, it shouldn't be blocking or critical. The manager should at least build the code, push it, and see the

> A "engineering manager" should have at least one task, it shouldn't be blocking or critical. The manager should at least build the code, push it, and see the unit tests actually run. With enough experience you should be able to spot things, eg, "HEY! There are no unit tests for this part!". If you're saying we don't need managers anymore because that's what our CI/CD pipeline does, I agree! I think a good manager has other responsibilities such as negotiating with other teams to enable their team's success. They don't need to understand the low-level details, but they should be able to comprehend complexity when explained, so even if I only produce '1' feature, they can be certain that my good job didn't produce '10' additional bugs to be discovered by the customers.