_25_11_2024_15_40_33.jpg)
_25_11_2024_15_40_55.jpg)
_25_11_2024_15_43_24.jpg)
|
Socoder -> Question of the Day -> QOTD: Refactoring |
|
| Sat, 10 Oct 2009, 10:49 | |
Phoenix
|
Do you take perfectly well-functioning code and change it to show no outward improvements at all, only implementation improvements? Is it worth the trouble? I find that it's time-consuming and an escape from the stuff that really needs to be done, but I do it anyway. Because I like pretty code, and I tend to change my mind quite often about what qualifies as pretty code. |
| Sat, 10 Oct 2009, 13:00 | |
JL235
|
If it's pretty for pretties sake, then no I try to avoid it. But I will sometimes reimplement small sections in order to make my code more extensible and durable. I also try to take the time to code it right the first time in order to avoid this kind of re-factoring in the future. |
| Sat, 10 Oct 2009, 15:26 | |
Jayenkai
|
I don't often get a chance to go back to code, these days, but if I am retweaking code it'll be purely for functionality rather than making the code look good. Most folk who've seen my code will testify to that! -=-=- ''Load, Next List!'' 
|
|
|
| |||
|
| ||||