Linked by snydeq on Tue 2nd Nov 2010 23:08 UTC
General Development InfoWorld offers a look back at the first decade of agile programming. Forged in February 2001 when a group of developers convened in Utah to find an alternative to documentation-driven, 'heavyweight' software development practices, The Manifesto for Agile Software Development sought to promote processes that accommodate changing requirements, collaboration with customers, and delivery of software in short iterations. Fast-forward a decade, and agile software development is becoming increasingly commonplace, with software firms adopting agile offshoots such as Scrum, Extreme Programming, and Kanban - a trend some see benefiting software development overall
Permalink for comment 448308
To read all comments associated with this story, please click here.
RE: terrible article
by dpJudas on Wed 3rd Nov 2010 04:16 UTC in reply to "terrible article"
Member since:

Not sure I agree.

Bad unit testing can be worse than no unit testing. Wasting your developers time writing a test that doesn't test anything properly is just a waste of time. Or worse, it tests that the code does what the code does thus making the test fail when you fix the code.

Even worse, an unit test is often described as the holy solution to all bugs, which again makes a lot of developers stop thinking about how to write resilient code. The unit test is supposed to find the bugs in it anyway. When the program then crashes at the customer, they conclude the unit test wasn't good enough instead of the way the code was written.

This is not to say that unit tests don't make sense, but I find the very overrated personally in the same way code reuse is often considered more important than any other requirements.

Reply Parent Score: 3