|
The World You Work In Job outlook, salary ranges, raises, layoffs, benefits--if it's important to you, we wanted to hear about it. We've compiled the results from the fourth annual STQE magazine/StickyMinds.com Salary Survey. Take a look at the state of the industry.
|
|
|
Make It Personal Often, despite all the data, the bugs, and the business case for quality, people don't make real changes until they discover what's in it for them. Bob Lee shows you how to make quality matter to those upstream.
|
|
|
Culture Clash Kathy Iberle reveals how her definition of quality changed when her job did.
|
|
|
The Seven Habits of Highly Insecure Software Severe functional bugs usually have pretty overt symptoms: an application crash, corrupt data, and screen corruption. Security bugs, though, usually have more subtle symptoms and habits. This article discusses the most common and difficult-to-notice symptoms of insecure software to help you track down these bugs during testing.
|
|
|
Wall-to-Wall Tools Got blank walls? Instead of hiring a decorator, perhaps you should enlist the help of a facilitator. This article examines how three experts use the wall in very different ways to make retrospectives, design, and collaboration better and easier.
|
|
|
Karl Wiegers on Software Inspections and Peer Reviews Peer reviews and inspections are among the highest-leverage software quality practices available. Here are some useful sources of guidance on how to perform software inspections and peer reviews, as well as some tools and online resources that can help you jump-start your fledgling review program.
|
|
|
A Look at PREfix by Intrinsa PREfix provides a source code simulation tool that is able to perform automatic review for a wide range of programming defects that lead to program crashes. Defects reported by PREfix include de-referencing NULL pointers, using uninitialized memory, leaking memory or resources, or using illegal values. Here is an analysis of the product.
|
|
|
The Two Bugs Brian Marick applies the philosophical concept of "ready-to-hand" to software programming and describes two bugs that illustrate problems caused by mismatched reuse of ideas.
|
|
|
Why Testers Should Participate in Early Reviews Do testers really belong in early reviews? For Michael Dedolph, the answer is yes! For that matter, he thinks more installers should be involved as well. Why? Testers and installers are usually involved in the "end game," so they add value by bringing that very different point of view to the review process.
|
|
|
When Assessments Are Relative Taking development and business contexts into consideration can mean the difference between a correct assessment and a useful assessment. Here's information on how to provide an assessment that's both correct and effective.
|
|