Re: Sourcing Metadata for Database Independence

Kenneth Downs <firstinit.lastn..._at_lastnameplusfam.net> wrote:

> You could instead commit 1000 hours to the engine/generator (put that
one
> unusual programmer on it, the guy who gets things done when left
alone),
> and devote another 4000 hours to having non-programmers spec out the
> metadata, and feed their specs into the engine and try zillions of
> combinations until they get what they like.
>
> The manager who believes that it will take 10,000 hours is tied
forever to
> the results of his decision: a crawling horror that must be
maintained
> until Judgement Day. Worse, the next job he does will be done the
same
> way, and he will put millstones around his neck one by one. The
toolmaker
> on the other hand, is tied only to a flexible tool that he can re-use
on
> the next job.
>
> I'd rather be tied to the tool :)

Sorry for chiming in late on this discussion.

Has anyone seen such a tool currently in use?

This approach sounds like the CASE tools of the '90's, which have not provided the promise they held out for a more flexible, re-usable applications development environment.

Nolan Madson Received on Sun Feb 27 2005 - 20:37:37 CET