But the point of a standard methodology is that its consistent throughout
the team AND outside of it. If you or one of your team left and went to
another company you might have to learn a whole new methodology and throw
out a lot of what you'd been using for years. With a standard, you would be
using the same methodology from one place to another and the same for
sharing fuses, etc. If it uses a different scheme than someone else, it
kills the reusability and shareability across companies/teams/etc. But I
guess a mini-methodology is better than none ;)
----- Original Message -----
From: "Pecora, James" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, April 13, 2000 9:19 AM
Subject: RE: Fusebox or not Fusebox that is the question...
> Bill - you are correct - FUSEBOX is just a methodology, any standarized
> methodology throughout a team environment will do the same thing. As for
> compartmentalizing the code for ease of debugging in the team..that can be
> part of your standard and not necessarily fe fusebox.
>
> Personally I use a method that is similar to fusebox in some way and
> diferent in other ways..
> I suppose it's the consistancy throughout the team that makes a standard
> usefull..
>
>
>
> -----Original Message-----
> From: Bill Killillay [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, April 13, 2000 10:20 AM
> To: [EMAIL PROTECTED]
> Subject: RE: Fusebox or not Fusebox that is the question...
>
>
> Can't all of that be done by establishing standards for a project or all
> projects. Why does it have to be Fusebox? I have been looking at Fusebox
> and I guess that I am a bit confused as to what it is and why I should use
> it over some other set of standards?
>
> FWIW
> Bill Killillay
> ICQ @ 8425781
>
> Emily B. Kim Wrote:
> > when you're working in a team environment, isolating pages makes them
> > easier to debug and also easier to reuse. for instance, we were working
on
> > an app and people were doing different parts of the app. the client made
a
> > change to the db and threw off one part of the app....a part i didn't
work
> > on. but i was able to fix it in 5 minutes 'cause i knew what the
> > fuseaction
> > was and that it was a query error so i just opened the query associated
> > with that fuseaction, and BINGO! it was fixed. i didn't even have to
look
> > at the rest of the code for that piece of the app.
> >
> > also, if you have a query that can be re-used - for instance to populate
a
> > table in one page and then a select drop down box in another page - it
is
> > easier to just write it once. you could even make it more flexible by
> > adding options for conditional processing. -emily
>
>
> --------------------------------------------------------------------------
--
> --
> Archives: http://www.eGroups.com/list/cf-talk
> To Unsubscribe visit
> http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or
> send a message to [EMAIL PROTECTED] with 'unsubscribe' in
> the body.
> --------------------------------------------------------------------------
----
> Archives: http://www.eGroups.com/list/cf-talk
> To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or
send a message to [EMAIL PROTECTED] with 'unsubscribe' in
the body.
>
------------------------------------------------------------------------------
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
