On 5/26/05, Giovanni Cuccu <giovanni.cuccu_at_gmail.com> wrote:
>
> Being a developer I can say that agile programming is nothing new,
> only a rebrand of some best practices. Some key point of agile
> programming are
> 1)unit test of waht you do
> 2)pair programming i.e. your work get reviewed by some other people
> Considering 1 and 2 I can think of Thomas Kyte as 'agile', I let you
> decide if programmer, dba or both
> Giovanni
>
>
That sounds like XP to me, I came across agile programming in the form of the
Agile Manifesto <http://agilemanifesto.org/> which to be honest filled me
with horror, I do understand where the imperative for this came from - I'm
rather afraid that it is railing against the wrong target. Most of the
projects and programming that I have come across have suffered from too much
speed and too little control and planning, trying to speed up an already
over hasty process and to advocate doing even less documentation and design
than we currently do seems to me to be an horrific idea.
As I say its probably a matter of personal experience, those of you with
excessively planned, specified and tediously documented systems and
development processes may well disagree.
--
Niall Litchfield
Oracle DBA
http://www.niall.litchfield.dial.pipex.com
--
http://www.freelists.org/webpage/oracle-l
Received on Thu May 26 2005 - 10:30:10 CDT
