Do you ever look at your old code...
ColdFusion...and hate it?
I notice that continually happens to me. Almost any time I revisit old code I am surprised by at least one thing I did that I would do differently now.
On one hand, I feel a very strong urge to re-write the darn thing...on the other, I feel like it is a good mile-marker for my progress as a developer. The fact that I can recognize better more efficient solutions to those old challenges means I am still learning.
Armand said:
Happens to me all the time (actionscript).
Actually, I think the day I look at my old code and say "wow! did I actually do something this clever?" I'd be very worried. :-)
Actually, I think the day I look at my old code and say "wow! did I actually do something this clever?" I'd be very worried. :-)
Andy J said:
I think looking back over old code is always good. Sometimes when you've been on a big project and followed it up with support you feel like you havent learnt or absorbed anything new. Then you look back and can sometime realised that you have progressed and your understandings have progressed
diamondtearz said:
I do that. I like to tell my self that it's a sign of development and improving insight. That may or may not be true but myself likes to hear that.
dan said:
If you look at old code and don't get sick to your stomach then you may have issues. I have the same problems but then I step back and think, this just means I am evolving as a programmer. When I think about it this way it makes it much more bearable. I guess it is just a is the glass half empty or half full type of view. Hope that helps!
Aaron Lynch said:
Yeah, these comments sum up my outlook on it. I don't like to see the old code, but I do like that I keep growing as a developer. So does that mean that the code I am writing today, will hopefully "suck" a month from now?
:)
:)
dan said:
Not necessarily, remember just because you find a better way to accomplish a task does not mean that the way you did it before was wrong. I have found better ways to accomplish tasks but older ways still work and to a customer that is all that matters. A customer is not going to pay you another 5 grand because you want to update your code
Peter Bell said:
I'm with Dave. I can live with the fact that my old projects suck. It is when I'm two weeks into a project and have been reading a bunch of architecture or coding books and now see how half-assed my approach was only two weeks ago when I started the project!
It's nice to be learning so fast, but it does suck a little to realize how dumb you were just a couple of weeks previously!
It's nice to be learning so fast, but it does suck a little to realize how dumb you were just a couple of weeks previously!
Kevin said:
Yeah the worst is when this process happens within one project...
I looked at some OLD code (like 5,6 years old) and saw my looping queries, and doing another query each loop because I knew nothing about joining!
Another I saw I was doing things in three or four steps that at the time there was a single function or tag that I never bothered to learn about...
stupid me :)
I looked at some OLD code (like 5,6 years old) and saw my looping queries, and doing another query each loop because I knew nothing about joining!
Another I saw I was doing things in three or four steps that at the time there was a single function or tag that I never bothered to learn about...
stupid me :)
ernest leitch said:
I like looking at my old code to see how far I've come. It also helps me get a better idea of what I need to change in my next project.
Loading....