This article was written based on a presentation given by Aristo Setiawan.

Test-driven development is a development pattern which is characterized by the use of pre-written test cases which are continuously validated via an iterative, incremental development process.

The basic process is:

1. Write the test.
2. Write the code which is tested by the test from step 1.
3. Validate that the new test and all previously implemented tests run successfully.

The process is repeated for each test until the code is fully implemented.

Benefits of test-driven development include:

• Forces simplicity in the code by breaking down complex tasks into individual subtasks.
• Ensures that the developer understands the intent of the code before writing it.
• Allows defects to be detected early in the development lifecycle.
• Prevents regression by identifying breaking changes prior to release of new versions of the code.

It is important for buyers of software to understand that a solution developed with automated testing (whether or not it is a result of test-driven development or build-then-test development) will have a higher up-front cost. However, automated testing can be expected to pay for itself over the total software asset lifecycle through reduced occurrence of bugs and the limiting of regression.

I want to share some resume writing tips. These are all based on actual things I have personally seen in resumes that I've reviewed for software developer positions. However, almost all of these tips are generally applicable to anyone writing a resume.

• Proofread for spelling and grammar, especially if English is not your primary language. When I see spelling and grammar mistakes I want to stop reading and throw the resume away. If you have these mistakes, you are digging yourself a hole and the rest of your resume has to be good enough for me to overlook these errors. If you are not adept at spelling and grammar, then find someone else to proofread your resume.
• Be specific and avoid using vague words such as "like" and "something." It is one thing to say you have a skill but it's completely different to describe how you have used a skill.
• Use a cover letter. Most people don't use a cover letter so by doing so you are already setting yourself apart from everyone else. The only exception to this is if you are responding to a job advertisement that specifically requested that you not include a cover letter.

More...