chris clarke
software development that works…or something
How can an application or language be Agile?
March 28, 2007 on 11:42 pm | In Uncategorized |From Interface21:
… Interface21 has taught Spring and agile J2EE to over a thousand satisfied students.
What is Agile J2EE? I’d really like to know.
If you sign up for a Spring training course, one of the topics covered will be:
Agile J2EE and lightweight containers
So Agile J2EE must be something to do with lightweight containers.
But hang on, there’s all these other things here:
There’s a bit of confusion as well, to a lot of the people involved with these books ‘Agile’ seems to mean different things.
For some it is simply using some form of NUnit, or TDD.
To others it is using bits of Spring instead of EJBs.
Many use the word ‘Agile’ in the ‘moving quickly and lightly’ sense, rather than the ‘Agile Methodology’ sense.
Some have the right idea but get it slightly wrong - declaring ‘Now let’s refactor!’ and proceeding to add more functionality to the code and make it more untidy.
This kind of thing makes you feel old and embittered - misunderstanding the meaning of ‘Agile’ in software development. To me, ‘Agile’ means lot’s of things but in summary it’s a set of experiences that people have shared that will help you get closer to software development that works. Here is an incomplete list of some of the things I would compile in to a book called ‘Agile Development With Agile’:
No Comments yet »
RSS feed for comments on this post. TrackBack URI
Leave a comment
How can an application or language be Agile?
March 28, 2007 on 11:42 pm | In Uncategorized |From Interface21:
… Interface21 has taught Spring and agile J2EE to over a thousand satisfied students.
What is Agile J2EE? I’d really like to know.
If you sign up for a Spring training course, one of the topics covered will be:
Agile J2EE and lightweight containers
So Agile J2EE must be something to do with lightweight containers.
But hang on, there’s all these other things here:
There’s a bit of confusion as well, to a lot of the people involved with these books ‘Agile’ seems to mean different things.
For some it is simply using some form of NUnit, or TDD.
To others it is using bits of Spring instead of EJBs.
Many use the word ‘Agile’ in the ‘moving quickly and lightly’ sense, rather than the ‘Agile Methodology’ sense.
Some have the right idea but get it slightly wrong - declaring ‘Now let’s refactor!’ and proceeding to add more functionality to the code and make it more untidy.
This kind of thing makes you feel old and embittered - misunderstanding the meaning of ‘Agile’ in software development. To me, ‘Agile’ means lot’s of things but in summary it’s a set of experiences that people have shared that will help you get closer to software development that works. Here is an incomplete list of some of the things I would compile in to a book called ‘Agile Development With Agile’:
No Comments yet »
RSS feed for comments on this post. TrackBack URI
Leave a comment
Powered by Cheese.
RSS Entries Feed.
RSS Comments Feed
^Top^