Timeline for How to get developers to do code reviews in a timely manner
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 26, 2012 at 13:09 | comment | added | Aadaam | Well, I worked in outsourcing. In outsourcing, most of the programmers aren't in because programming is fun, they are in because programming has the best work/pay ratio, with rates much higher than anything else... they hate it like any other job.. and they try to do everything to further "optimize" this ratio, if you know what I mean... | |
| Jul 26, 2012 at 12:36 | comment | added | gnat | @Aadaam your experience definitely differs from mine - not only with regards to post-commits, but also (and especially) wrt part of "Programmers are lazy..." As for managers having more realistic image I agree that was typically the case in my teams; it only did not led managers I used to work with to senseless ideas about what kind review to force | |
| Jul 26, 2012 at 11:58 | comment | added | Aadaam | Post-commit hurts your code quality terribly in my experience. Programmers are lazy, and they will feel they're done if it can be committed: "yeah, well, it's not perfect, but who the f.ck cares, what's perfect in life? it does the job, doesn't it?" the only good answer is NO, and perhaps the managers have a more realistic image of programmers than they have about themselves, that's why they require pre-commit (or at least, pre-merge) code reviews. | |
| Jul 26, 2012 at 9:57 | comment | added | Giorgio | "If company knows better than programmers, why don't they write the code themselves?": very good comment! But I would hope that development managers are former developers themselves. | |
| Jul 26, 2012 at 0:57 | history | edited | gnat | CC BY-SA 3.0 | added 73 characters in body; added 152 characters in body |
| Jul 26, 2012 at 0:46 | history | answered | gnat | CC BY-SA 3.0 |