I think there are really two separate phases of developing an application.
The first one is everything that occurs before you start coding, and the
second one is the actual coding. Steve's SecretAgents concept applies only
to the second phase - coding. And for that I know it works.
Steve's not trying to accelerate the design and specifications phases (in
XFB terminology, that would be wireframing and prototyping), nor is he
claiming that architecting an application will fall under the 48 hour
window.
The radical concept is that once those steps are out of the way, and a
competent, experienced architect has written Fusestubs (Fusedocs in an
otherwise empty file) for all the fuses, it will only take a day or so to
have the actual coding done, by using a distributed development approach.
NAT
> -----Original Message-----
> From: John Quarto-vonTivadar [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, August 23, 2001 8:53 AM
> To: Fusebox
> Subject: Re: What about the 24/48 Hour coding?
>
>
> > > What do you think about the 24/48 Hour Coding project
> > > supposed by Steve Nelson (www.secretagents.com).
> > >
>
> I think it's a great idea in the right context. I think the biggest hurdle
> with it, is that developers, being analytical types, will push
> the idea past
> where it should go from a business perspective. You might be able
> to get the
> project done in 2 days, but is your client *prepared* to have the project
> done in 2 days? Most client need a few weeks just to get in tune with what
> they really want.
>
> If the client isn't ready in 2 days, two big effects will emerge:
> first, the
> fact that the work can get done fast will just exacerbate the problem of
> "rushing" through the planning stages of project development ("since the
> time cost of errors is so low, may clients and many developers will just
> choose to pay it rather than do it right the first time").
>
> Second, the client will demand drastically reduced prices. Perception in
> this case is much more important than reality (how else does Neiman Marcus
> get customers to pay $500 for a shirt?). I've yet to meet a developer who
> couldn't resist boasting to a client that he got the job done in
> 1-2-3 days
> (when the client was expecting several weeks). The client is impressed the
> first or second time this happens--after that, he comes to expect it not
> because you're brilliant but because you've trained him to.
>
> The upshot of that is that you will find fewer and fewer clients who will
> pay $50,000 for a project that takes 2 days to complete, whereas
> there would
> have been many more who would pay such a fee for a month-long project *if
> the developers had just shut their mouths about their development time*.
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
