Structure marking is a programming technique that defends data against damage, especially from software bugs. It adds flags to data structures and checks them at each use to detect damaged data immediately.
Team building sessions: few like to attend those things. Yet, the benefits of teamwork are constantly praised and rewarded. Even this article praises teamwork, but does not suggest any touchy-feely exercises to bring test and development teammates closer together. Deborah Kablotsky specifically covers understanding each other and working together throughout a project's lifecycle, a proven way of working together to shorten test cycles and deliver high quality products on time. She also discusses the necessity of integrated teams and provides some proven tips successful to Web-based businesses on making this best practice a reality.
Modern optimizing compilers are becoming increasingly dependent on dynamic profile information. Because the profile information collected by these compilers also is sufficient for QA, it is likely that code-coverage analysis will become an integrated development environment option. This integration should help to simplify your code development and testing processes and should also improve the accuracy of your coverage information and the performance of your optimized code.
Design thinking points out several missed steps in software development. And, while some may believe ideation and iteration to be wasteful, they're easy to add to the development process at low cost and, in the end, result in substantially more valuable software. In this article, Jeff Patton describes the four basic steps of design thinking.