While that’s true and I do document my code, I still get the urge to rewrite big parts of it. In the end I will in fact rewrite it, but that’s because I want to turn the original version of the code into a more general system that I can then use for my future work/projects.
As long as you’re doing this for fun/function and not because you’re embarrassed, then that’s fine. :p I wrote my own tween library in javascript purely because that just sounded like a great weekend, haha.
Really? I have almost the exact opposite experience when I look at my old code.
I’m usually afraid that it’s junk and I could’ve done better, but then I’m routinely impressed by what I’ve written and go “Man, I did a good job with this.”
Then you never had to look at your old code (that tends to be of way worse quality than what you are currently coding due to improved skills) xD
I look at my old code all the time.
If you keep things organized and well documented, its poor quality really shouldn’t bother that much.
While that’s true and I do document my code, I still get the urge to rewrite big parts of it. In the end I will in fact rewrite it, but that’s because I want to turn the original version of the code into a more general system that I can then use for my future work/projects.
As long as you’re doing this for fun/function and not because you’re embarrassed, then that’s fine. :p I wrote my own tween library in javascript purely because that just sounded like a great weekend, haha.
I will turn it into a general system for two reasons:
1: Because I know I can rewrite my old code in much better quality
2: Because this is something that I and my work colleagues may need regularly, so we dont have to rewrite it from scratch every time.
Really? I have almost the exact opposite experience when I look at my old code.
I’m usually afraid that it’s junk and I could’ve done better, but then I’m routinely impressed by what I’ve written and go “Man, I did a good job with this.”