A news wrap-up of our most recent research report which discovered a staggering number of industries with applications still vulnerable to Heartbleed-style attacks. Continue reading
Most IT organizations wouldn’t consider the software risk in their application portfolio a brand issue; that is, until they experience a tragedy or crisis such as application failure and customers start to worry. Most of the time IT organizations are able to calculate the cost to fix the problem and how it will affect their overall business. However, what often isn’t taken into account is the long term effects on their brand and business going forward. Continue reading
The current state of measuring the environmental impact of our IT infrastructure is missing a big piece of the puzzle. One of the metrics we use, power usage effectiveness (PUE), only looks at how much power entering a data center is being consumed by the computer hardware in relation to the total amount of energy the facility uses.
But what about the millions of lines of code running on that hardware? How can we know if that’s energy efficient code?
Just like a species of insects can become resistant to a certain type of pesticide, a new strain of software bugs has emerged and is plaguing software developers and wreaking havoc on software quality — architecturally complex violations. Unlike a code-level bug, a system level defect involves interactions between several components, often spread across different levels of an application, making them much more difficult to find and fix.
And even though these types of violations only account for 10 percent of the total number of defects, they lead to ninety percent of the production issues — severely impacting software quality and technical debt.
When one of our writers, Lev Lesokhin, started contributing to Wall Street & Technology he was shocked to find very little on the subject of technical debt. Considering how much the concept intersects the worlds of finance and technology, he thought he’d find whole forums of IT guys and financiers exploring the intricacies en mass.
When he realized that was far from the case, he set out to create a guide to bridge the gap and get the conversation started. By taking some of the more complex concepts of technical debt and translating them into financial language, he hoped to bring the technical jargon out of the CIO boardroom and decipher it for a financial audience.
Despite mounting evidence that the use of fossil fuels will damage our environment, humanity appears hard pressed to find an alternative. And even though environmentally friendly options have presented themselves, we have one foot firmly planted in the past. Working in the IT industry, it’s astounding how closely this resembles our current state of agile software development and testing.
Even though the industry identifies that a problem exists, and have the tools available to fix it, its dead set on sticking to “the way it was.”
Our colleague Vijay Anand recently penned an article exploring this topic and outlining what software development teams can do to maintain their current level of production, without sacrificing software quality. Read the full story HERE!
In the past decade, it’s become even more obvious that reducing software risk has one of the strongest correlations to cost and overall impact on the value of all applications. That is why last month we organized a CIO conference with our partners Steria in Belgium focused on software risk and productivity management. The objective of the conference was to identify a roadmap for efficient software risk and productivity management practices to better control cost, minimize risks, and increase the value of enterprise applications.
Don’t miss out on our videos from the conference exploring reducing business risks and improving productivity.