Linkopedia June 2009

Published June 10th, 2009 Under Links | Leave a Comment

How TDD and Pairing Increase Production

Continuous Integration On A Real, Big Project

Agile is NOT a Project Management Methodology

SmartGWT is a GWT based framework that allows you to not only utilize its comprehensive widget library for your application UI.

Webmasters and web developers can use Page Speed to evaluate the performance of their web pages and to get suggestions on how to improve them.

Article: How Scrum Helped Our Team

Article: A multi-tier architecture for building RESTful Web services

Video: Applying User Testing During Development

Video: Practical Functional JavaScript

Video Interview: Bas Vodde on Large Scale Scrum

Video: Effective Java Reloaded

Find more interesting links on the software development links directory, the software development tools directory, the software development articles directory, the software development blogs aggregator or the software development videos directory.

Looking for Agile Blogs

Published March 9th, 2009 Under News | Leave a Comment

I have recently created a new web site AgileVoices.com that aggregates for RSS feeds concerning agile software development. If you know about a good blog feed that is missing from the current roster, I would be please to add it. Thanks for your cooperation.

Summer 2008 Issue of Methods & Tools

Published June 23rd, 2008 Under Methods & Tools | Leave a Comment

Methods & Tools is a free e-newsletter for software developers, testers and project managers. Summer 2008 issue’s content:
* UML versus Domain-Specific Languages
* We Increment to Adapt, We Iterate to Improve
* Building Products with Acceptance TDD
* Getting and Keeping Control over your Project

60 pages of software development knowledge.

To download or read this issue go to http://www.methodsandtools.com/

The Three Rules of Test Driven Development

Published March 3rd, 2008 Under Quotes, Software Development | Comments Off

Over the years I have come to describe Test Driven Development in terms of three simple rules. They are:
1. You are not allowed to write any production code unless it is to make a failing unit test pass.
2. You are not allowed to write any more of a unit test than is sufficient to fail; and compilation failures are failures.
3. You are not allowed to write any more production code than is sufficient to pass the one failing unit test.

You must begin by writing a unit test for the functionality that you intend to write. But by rule 2, you can’t write very much of that unit test. As soon as the unit test code fails to compile, or fails an assertion, you must stop and write production code. But by rule 3 you can only write the production code that makes the test compile or pass, and no more.

If you think about this you will realize that you simply cannot write very much code at all without compiling and executing something. Indeed, this is really the point. In everything we do, whether writing tests, writing production code, or refactoring, we keep the system executing at all times. The time between running tests is on the order of seconds, or minutes. Even 10 minutes is too long.

Robert Martin

http://butunclebob.com/ArticleS.UncleBob.TheThreeRulesOfTdd

Besides these rules and independently of an agile approach, I always like as a developer being able to verify quickly my code, because it makes much more easier to find all the errors I do ;o)