Yeah, that's a major obstacle to automation. The bug that prompted this thought was more subtle than yours: it wouldn't have affected speed or performance of the compiler itself, but would have adversely affected performance of generated code (though how much, I couldn't tell you - highly branchy code would be more badly affected).
I moved one line outside a loop (since it only needed to be run once), and that made the code a lot faster
Look, no optimising compiler! :-)
I think that code reviews are supposed to be cooperative rather than competitive.
Excellent point. That argues in favour of not deducting points for bugs, and preventing collusion through social pressure - which shouldn't be a problem in a small enough team for the basic idea to work.
Re: Incentives
Yeah, that's a major obstacle to automation. The bug that prompted this thought was more subtle than yours: it wouldn't have affected speed or performance of the compiler itself, but would have adversely affected performance of generated code (though how much, I couldn't tell you - highly branchy code would be more badly affected).
I moved one line outside a loop (since it only needed to be run once), and that made the code a lot faster
Look, no optimising compiler! :-)
I think that code reviews are supposed to be cooperative rather than competitive.
Excellent point. That argues in favour of not deducting points for bugs, and preventing collusion through social pressure - which shouldn't be a problem in a small enough team for the basic idea to work.