While the definition of Web 2.0 has barely begun to settle down, applications must start to react. Web 2.0 is, from a technology viewpoint, mostly a combination of collaborative web technology and application web interfaces that mimic their native client counterparts. From a social viewpoint, it's a communication and information transition: blogs, Facebook, integrated chat, and meeting capabilities create a web base of knowledge so that anyone can search for anyone or anything and communicate or contribute to the subject matter. From a CM/ALM perspective, there has always been a need to have a base of knowledge, of data, and of people. The success of CM depends on it. So how really does Web 2.0 play into the next generation of CM?

In this Sticky ToolLook interview, Danny Faught shares insight onto his earliest days as a tester, the skills he's acquired throughout his career, and skills and tools he believes every tester should posses.

After more than thirty years in information technology, the last fourteen spent focused on testing and quality assurance, Dale Perry has come to believe everyone can benefit from thinking like a tester. In this article, Dale offers comical, yet serious, insight on how a tester views airport bathroom stall designs.

How often have you or one of your teammates checked the source code into the code library which then instantly triggered an automated build?  How many times did this instant build succeed? Do you have an automated build and release system that ensures your software is built in the same way each and every time? Are deployments to staging environments entirely automated and executed with a single click? While reviewing a defect in a production release, are you able to backtrack through the source code changes and identify the root cause of failure? If the last good checkin happened a few days ago, identification of this root cause of failure would become even more difficult. Seasoned CM practitioners advise that you perform a daily build to avoid such integration issues. What an irony it is that only a few projects take advantage of this simple, yet powerful technique known as Continuous Integration (CI).