Timeline for What do you do when code review is just too hard?
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 4, 2016 at 6:12 | comment | added | Allan S. Hansen | This is a good answer, because while many of the others are technical more correct - this takes offset in the real world and while we all want to live in a world where everything is well tested, well documented - we don't. Legacy code, strange implementations, misunderstandings, unreasonable stakeholders, bad weather ..... life will throw bad stuff at you and you'll have to deal with it. | |
| Jul 1, 2016 at 8:48 | comment | added | Ben Hillier | I've experienced most of the above so many times it's depressing. I mixture of shoddy programming practices, moving goalposts and unsympathetic management deadlines means that what we all know should happen, and what really happens, are two very different things | |
| Jun 30, 2016 at 14:00 | history | answered | Yakk | CC BY-SA 3.0 |