Alan -
You seem to have thought this through thoroughly. I have one more addition
for this maybe-dream:
Just how architects can destroy a fuse coder's reputation by saying they do
shoddy work, so can the fuse coder destroy an architect's work by letting
people know that their documentation, FDs, etc. really suck. The thumbs-up,
thumbs-down goes both ways. It's up to architects to write good specs, and
coders to write good code.
NAT
> -----Original Message-----
> From: McCollough, Alan [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, April 05, 2001 9:06 AM
> To: Fusebox
> Subject: RE: Fwd: extreme programming
>
>
> Imagine a world where instead of daytraders, you have daycoders.
> You get the
> specs for one single CF template, read 'em, code it, and turn it
> back in an
> hour. And cha-ching, you get a hundred bucks. Or mabye fifty. Or if Hal's
> Filipino friends lock in on this action, you'll get a dollar and fifty
> cents. Hm, what's the Filipino peso trading at this morning?
>
> Anyhow, yes, I can see that if indeed a solid "black-box" protocol is
> developed, where a coder could pick up a spec and return a completed CF
> template, an automated service such as something running on
> www.secretagents.com could indeed broker out CF template development in a
> check-in, check-out paradigm, combined with a competitive bidding
> structure.
>
> As a coder, you would register with the service in a fashion similar to
> EBAY.
> As a code architect looking for coders, you would submit complete
> code specs
> to the server, and you would have the $$$ for payout in i-escrow, or some
> other on-line escrow account. Along with the code specs there would be a
> maximum payout for each code block, which I define as a single or group of
> related CF templates that will need to be coded up. These will be
> treated as
> a logical unit, with a dollar value, and a time constraint.
>
> There would be a disclosure period, say 1 week, where prospective coders
> could bid on specific components. The bidding would start at the
> fixed max,
> and be a downward bid, with lowest bid winning.
>
> At the end of the disclosure period, the winners get an access code, and
> they check out their chunks and start coding. If it should happen that not
> all of the code chunks sold, the code architect will have the
> opportunity to
> cancel the entire project, or re-list it again, with perhaps an increased
> max payout. Of course, any additional $$$ will have to be uploaded to the
> i-escrow account.
>
> During the code phase, the coder can upload their code chunk to the app
> server so it can be hooked up to the test harness and verified.
>
> If the coder succedes in producing validated code in the time limit, the
> money is unlocked from i-escrow, with of course a 10% skim off the top for
> whoever writes this wonderful code brokerage app. If the coder fails, the
> code architect is given the opportunity to allow the coder some
> slack, or to
> ban that coder from bidding on any further projects for that architect.
> Imagine the thumbs-up, thumbs-down in the gladitorial arena, if you will.
>
> So, in this environment, a freelance coder would register with
> the service,
> and just sit at home and bid on pieces of projects. Because of the
> code-chunk paradigm here, you would get that wonderful parallel coding
> phenom where instead of one human coding for a thousand hours, you get a
> hundred folks coding for 10 hours each.
>
> Say, maybe I should quit workin' for Uncle Sam and do this on my own...
>
> > -----Original Message-----
> > From: Steve Nelson [SMTP:[EMAIL PROTECTED]]
> > Sent: Wednesday, April 04, 2001 7:17 PM
> > To: Fusebox
> > Subject: Re: Fwd: extreme programming
> >
> > i want to take your 2 month development time down to 1-2 days (after the
> > specification is complete). This would be done by having anywhere from
> > 1-100 Fusecoders on the project. According to the mythical man month,
> > this isn't possible because adding manpower to a project won't speed up
> > development. Common sense tells me that it's because no has figured out
> > how to linearly manage people.
> {redacted}
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
