Money: SOMETIMES Re-Engineering is cheaper, but the long run maintenance costs could be higher as the code base gets harder and harder to read, it's not a question of what is cheaper, but when you want to spend your money, now (in a new one), or later (in a re-engineer)

Time: The more code there is to understand how to re-engineer, the longer it will take, to a point where it will eclipse the amount of time that it would take to rebuild the site. If you're dealing with a large code base, might be better off to start from scratch.

Experience: Typically re-engineering is something that requires some experience in. If the staff has been living and breathing Cold Fusion, a Re-Engineer might be feasible because they will understand what can and will go wrong. Otherwise start from scratch, and there is less to go wrong if you know your own code.

Scope: Take a look at the spec, is the entire site covered in a re-engineer? In other words, if it looks like you are starting a new project, do just that!

Support: Is the original developer(s) available? Things get significantly harder if nobody knows the code.

Ok, food for thought here, questions, comments?

Gregory Harris Web Developer ____________ The Stirling Bridge Group, LLC *We Engineer Internet Business Solutions* TEL: (949) 707-1534 FAX: (949) 707-1535

----- Original Message ----- From: "Jay Jennings" <jennings@elltel.net> To: "Fusebox" <Fusebox@houseoffusion.com> Sent: Thursday, May 10, 2001 10:27 AM Subject: Porting Old Site

> I'd like some advice from the FB crowd... > > I'm reworking a site that was kind of built in fits and starts over the past > few years. The thought at first was that I'd just change code that is > affected by the new data integrity restraints in the database, but as I get > into it I'm starting to think that rewriting from the ground up might be the > better option. > > Here's some details...the current site was NOT done with fusebox but > eventually we'd like to port it that way. We're not changing any of the > screens at this point -- it's all behind the scenes changes. > > So, since we have a new database, and we have a prototype (the current > working site), I'm thinking we'll have fewer headaches if we just build the > new fused site now, instead of tweaking this one and porting it to fusebox > later. > > Has anyone done this kind of thing? Am I correct in thinking it won't take > longer to build from the ground up -- especially since the current site can > be used as a spec? > > Thanks. > > ..jj.. > > - - - - - > Get your free email account: you@alakazam.com > Sign up at http://www.alakazam.com > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm

Archives: http://www.mail-archive.com/fusebox@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists