Timeline for What are common code review processes and what is considered bad?
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 19, 2013 at 20:59 | comment | added | Dunk | 100% agree with the last paragraph:You should discuss your intended design before implementing. At least then you are starting with a supposedly acceptable framework. Then after implementing, it might be worth yet another shot at discussing the final design (not code). Then modify the code to match the outcome of the final design discussion. If after a couple of tries at that and it doesn't improve matters then that should make it obvious that the position is just a bad fit and you should start looking elsewhere. | |
| Dec 19, 2013 at 20:44 | history | edited | Juanmi Rodriguez | CC BY-SA 3.0 |
added 524 characters in body
|
| Dec 19, 2013 at 20:35 | history | answered | Juanmi Rodriguez | CC BY-SA 3.0 |