Well Dave - First, thanks for not restraining yourself. If I wanted people to restrain themselves - I probably wouldn't have asked the question in a public forum. So, I appreciate you chiming in. ;)
Your quote - and the article it links to - more or less hits the nail on the head - and gets at what I was trying to ask. (Although maybe not as clearly as I wanted) ""Premature optimization" is a phrase used to describe a situation where a programmer lets performance considerations affect the design of a piece of code. This can result in a design that is not as clean as it could have been or code that is incorrect, because the code is complicated by the optimization and the programmer is distracted by optimizing." So - what I was more or less asking about my code - was more or less - Was it good design? Or should I have thought of it a completely different way? And of course - in thinking of it a different way - could I have made it faster (or improved performance). To me - Good Design is both clean - AND fast. I understand there is give and take - I am trying to find out what those are in regards to this scenario. Now I will come out and say it - I don't consider myself a "programmer". I'm the "Half-Breed" - the Graphic Designer who has found himself becoming a programmer out of necessity. I have no "formal training" other than reading the CF-Wack a few dozen times. I am continually trying to learn new things and improve my code... So that being said - - Leigh's approach is completely different from what I would have thought of -and I am really appreciative of the insight- and in the interest of learning through enhancing application performance I am asking questions about whether that is "faster" or a truly "better" approach. I myself have NO idea. So - using that concept of 100 years of Dates stored in a DB - is that a better way to design an application rather than using/looping DateAdd()? (Especially If you only need to get at 30-90 days of dates at a time) I certainly don't know - so I thought I would ask to see what Leigh and Others think? To myself, it seems completely counter-intuitive to re-create a calendar. But to add another quote "We don't know what we don't know." And - I know, I don't know. Ya know? I would also add - that this probably doesn't exactly fall into the "Premature" category. The code is completed and it works. Now am I wondering the different ways it could or should be improved upon... And more importantly - if there is a general consensus among the group as to what I should NOT do. There are some very simple things happening in this code - and methods/approaches I use on a regular basis. So I figured this would be a good piece of code for me to see if others have input. Does that make sense? I mean - what I really "want" here is either: 1) Boy, it's pretty straight forward, changing it really won't get you much if anything. - or - 2) If you did it this way you get A,B and C - Nick ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:329739 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
