It's a small win for green computing, a balancing act for software testing, and the acknowledgment that the most dangerous component in any given computer system isn't the fault of either programmers or engineers in today's Test Center Tracker. Green Gets Small: When you can take a low-power computing option and build it into a tiny package that reduced the need for raw materials and manufacturing energy, then i It’s a small win for green computing, a balancing act for software testing, and the acknowledgment that the most dangerous component in any given computer system isn’t the fault of either programmers or engineers in today’s Test Center Tracker. Green Gets Small: When you can take a low-power computing option and build it into a tiny package that reduced the need for raw materials and manufacturing energy, then it’s a green win from start to finish. That’s what Artigo has done with their latest development system, and Ted Samson takes a close look over in Sustainable IT.The Testing Touch: When you build any software system, testing is a critical part of the development process. Who, though, should do the testing — should it fall on the shoulders of those inside the development organization or on those of outside engineers with no “skin in the game” of development? Zack Urlocker looks at the pros and cons of inside and outside testing in Open Sources and reaches a balanced conclusion. The Most Basic Vulnerability: There’s no real disagreement: the most dangerous component of any computer system is the user who sits at the keyboard. How should you patch this critical vulnerability, and what can you do to protect the system if the vulnerability must go unpatched? Matt Hines asks the question in the Zero Day Blog, and finds a long list of suggestions. Technology Industry