Gyrus,
My opinion is that of only one person, and not of several. One thing to take
into consideration is that the person(s) that succeed you may or may not
have fusebox knowledge. I for one picked it up while it was FB2 which was a
relatively easy concept to grasp. It has done a major overhaul and FB3 is a
different animal to learn, if you have not done any FB in the past.
I guess it would be up to the company you work for to hire the
appropriate developers for the task, but they would be searching through a
much smaller realm of CF developers which had FB knowledge.
If it is your feeling that the the application may in fact go through
some major overhauls and enlargement in the future, where they are going to
need more than one developer to take care of things, I would say by all
means give it a facelift in FB. If for no reason other than learning FB. The
way I look at it, is that this is an opportunity to learn something that may
very well increase your value as a developer, and it is good to start on a
small scale. I only prefer it on larger applications like I stated above,
and I can code faster without it on smaller applications, but it is every
man/woman for themself and everyone has to choose what is best for them. I
do not think that FB would hurt you current client!!
DB
----- Original Message -----
From: "Gyrus" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Saturday, November 17, 2001 11:24 AM
Subject: Re: Fusebox - opinions?
> > I am only
> > interested in using it due to having more than 1 developer. I can code
the
> > Coldfusion and tell the DBA what queries I need and then just plug them
in
> > without him having his hands in my app.
>
> I am currently doing a lot of work (freelance) for one client, an
> agency. I'm pretty much their main CF guy, and I'm thinking of
> starting to use Fusebox for these reasons:
>
> - I've learnt a lot recently and I'm on the verge of redoing the
> 'app templates' I've got, to standardise a lot of things in the way
> I work.
> - The stuff I'm doing is usually relatively small, and just me coding,
> but I want to implement some sort of standard app structure for
> future scalabililty.
> - Also, there's no guarantee that I'll be with them in a year's time,
> and I'd like to leave them with stuff that can be maintained/
> scaled easily by my successors.
> - They're getting more and more ambitious projects coming in,
> and I'd like to implement some sort of structure/standard before
> the going gets crazy!
> - I'm organised enough to invent my own standard structure, but
> I thought, why reinvent the wheel, esp. when there's a wheel out
> there that so many others are already familiar with?
>
> Is Fusebox overkill in this situation, even with these 'future'
> considerations?
>
> - Gyrus
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Get the mailserver that powers this list at http://www.coolfusion.com
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
