Timeline for When to refactor
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 29, 2017 at 10:21 | comment | added | R. Schmitz | #2 sounds very snobbish and is actually useless for evaluating code. #3 & #4 not every company uses unit tests. #8 Avoid comments wherever possible, and 100 lines is waaay too high. I have 1 big widescreen monitor in portrait mode and I would barely be able to see the whole function at once. If it's more than 15 lines of actual code, there should already be a solid reason why you keep it that way. It's a nice, practical approach to have a checklist, but too many points here are just made up or use random values without any reasoning behind it. | |
| May 16, 2013 at 12:46 | review | First posts | |||
| May 16, 2013 at 13:14 | |||||
| May 16, 2013 at 12:30 | history | answered | Mainguy | CC BY-SA 3.0 |