A question for any code jockeys

[keith - SuPeR K!]

If you build this strong foundation, won't it be reusable for other projects? After years of building websites from scratch I finally got a to a point a few years ago where I asked myself "Why am I starting from scratch every time?" Since then I've built up an entire content management system that runs most all of the projects I build. While I still have to go back and recode some parts of the various functions on occasion, the function names and output formats are the same so I can just upload the new version to my older sties and they automatically get the new bits and better functionality without really breaking anything in the process. While I've spent years working on my CMS project, it's still not 1.0, but it works just fine and in the long run it has saved me a ton of work! Plus, I can eventually package and resell what I've done once I feel it is ready.

Take your time devising the base. I've rewritten mine several times when I found better ways to do things, but it's been worth it to me to have that stable base to work off of.

[Ghoulish Delight]

Originally Posted by scaeagles

Didn't mean to insult intelligence.

None taken. Just rereading my post, and your response, and realizing that really the answer was obvious (I practically answered it myself in my OP by pointing out how useless all my old "get it done" code is).

Originally Posted by keith - SuPeR K!

If you build this strong foundation, won't it be reusable for other projects?

Oh, no doubt. I'm definitely designing this to be a "test script platform" rather than a collection of test scripts. But there's only so long I can write code to parse config files and handle exceptions before I want to see some freaking lights blink!

I think I'm approaching the point where I can do some #DEFINEs to temporarily shore up some holes in a way that lets me go back later and improve. Just trying to find where that line is.