|
|
|
|
|
by atq2119
10 days ago
|
|
Of course it does, but that's beside the point. As a software developer, you must never subject your team mates to a PR that you yourself believe to be low quality. The point of code review by others is to catch things that you missed. There are multiple lines of defense for quality. Yes, automation can and should be one of them, but your own self-review always has to come before review by your team mates. |
|
However, from an operations perspective, a dev is a piece of the qa pipeline with a nonzero error rate, and an optimal throughput rate, above which that error rate rises dramatically.
As a dev, you'll never merge a bad PR; in ops, we want to help you with that goal, and also have plans for what happens when it fails.