Jeff,
You keep on going on about other methodologies. Which particular other
methodologies using CF are publicly available? You keep mentioning all
these other methodologies, but can we at least compare them to Fusebox?

Fusebox is probably one of the best methodologies (if not the only public
methodology) available for a ColdFusion developer. The book also covers a
number of fundemental design elements that any CF'er should understand.
EVEN if they don't do Fusebox.

Adam


-----Original Message-----
From:   Jeffry Houser [SMTP:[EMAIL PROTECTED]]
Sent:   Thursday, December 21, 2000 1:47 PM
To:     CF-Talk
Subject:        Re: Fusebox



"Warrick, Mark" wrote:

> The fusebox methodology has many benefits, and I really don't think it
adds any time to the development cycle.  In fact, I'm pretty sure it helps
speed up development.
>

  Well, that has nothing to do w/ Fusebox.  Any programming methodology
will offer
this benefit.  The key is having one in place and sticking to it.


>
> One of the greatest advantages of the style is that you can modularize
you code, and in doing so, you can assign pieces of your application to
various developers without worrying about them stepping on each other's
toes.
>

  See above.  This is not unique to fusebox.



>
> Another advantage is that certain companies (such as mine) require it. 
So if you don't do it, you're not going to get a job with certain
companies.
>

  If you are not a consultant, that is complete hogwash, I think. 
Especially with today's job market.  Fusebox (or whatever methodology the
company uses) should be more than
willing to train on the methodology.  If you already know the language
(What company
doesn't have enough trouble finding people who know the language?),
learning the
coding practices should be easy enough.

  I did one job, where the first thing they did was sit me down and
outline the
coding practices.  It took about a half hour sitting down with the lead
developer.
I took notes, and then followed them.  No problems.


>
> Lastly, it's very simple to follow the programming flow of a fusebox
app.  When something goes wrong, you simply search for the fuseaction in
the index file and then you'll see right away all the templates in a
single handy block that could be involved with the problem.
>

  As I said previously, any methodology worth its salt should offer this. 
If
I don't know fusebox, then your app isn't going to be any easier to follow
than
some other unknown methodology.  (It probably will be easier to follow than
random coding, though)

--
Jeff Houser | mailto:[EMAIL PROTECTED]
AIM: Reboog711  | ICQ: 5246969 | Phone: 860-229-2781
--
Instant Cold Fusion 4.5  | ISBN: 0-07-213238-8
Due out 3rd Quarter 2001
--
DotComIt, LLC
database driven web data using ColdFusion, Lotus Notes/Domino
--
Half of the Alternative Folk Acoustic Duo called Far Cry Fly
http://www.farcryfly.com | http://www.mp3.com/FarCryFly
--
Promise me no dead end streets, and I'll guarantee we'll have a road
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        Structure your ColdFusion code with Fusebox. Get the official book at 
http://www.fusionauthority.com/bkinfo.cfm

Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists

Reply via email to