Lists Home |
Date Index |
Title: RE: [xml-dev] Web Services Best Practice (was: Interesting XML-DIST-APP thread)
> -----Original Message-----
> From: David Starr [mailto:email@example.com]
> Sent: Saturday, January 12, 2002 6:02 AM
> To: firstname.lastname@example.org
> Subject: RE: [xml-dev] Web Services Best Practice (was: Interesting
> XML-DIST-APP thread)
> > I've lost track of meandering of this thead, so this
> > may or may not be a response to my suggestion for
> > staying away from the proprietary wizard tools for
> > building web services.
> Sorry, it was a rather tongue-in-cheek response to Rob
> Griffin's assertion
> that RAD and drag and drop tools lead to systems that are
> poorly designed.
> According to Rob's sig he works for Quest Software which makes some
> excellent GUI and drag and drop tools for managing databases.
> I believe that in many cases that choosing good tools can
> lead to great
> productivity gains. Well tested program generators also have
> the benefit of
> creating quite reliable code. I don't generally use tools unless I
> understand what they're doing under the hood. I don't know
> if more poorly
> designed code comes from GUI tools or not. If it does, then
> we have to ask
> ourselves if it's because people turn off their design skills
> when using the
> tools, or whether it's because the tools simplified certain
> tasks to the
> point where they allow people to attempt certain development
> tasks for which
> they would otherwise be ill-prepared.
Not to disparage our own tools, but a tool that allows you to
convert code from one paradigm to another 'instantly' is going to
lead to a lot of poorly performing systems unless developers realize
that they have to refactor the code. The advice in the artice I
cited doesn't recommend that, just a 'tips and tricks' style quick fix.
Web site: http://www.quest.com