There's bad news ahead for organizations that focused on a bimodal IT approach. According to research firm IDC by 2019 80% of those firms will have accrued crippling amounts of technical debt leading to increased complexity, cost, and a hit to their reputation.
Is the Bimodal IT Approach an Invitation to Failure?

Insurance organizations have reached a tipping point. Historic institutions, with in some cases hundreds of years of service, they are being forced to transform due to changing consumer demands and nimble, technology-centric startups bringing innovative products to market. No stranger to regulatory and privacy concerns, Insurance carriers have overcome many roadblocks throughout their lifetime of doing business. Now they must tackle their legacy IT systems and improve software risk management to deliver the value today’s market is after.

The Insurance Industry Challenge: Improve Software Risk Management
Get the Pulse Newsletter  Sign up for the latest Software Intelligence news Subscribe Now <>
Technical debt has not only become a popular industry term, but it has proven itself to be an important concept.
The Human Side of Technical Debt
Open source is part of almost every software capability we use today. At the  very least libraries, frameworks or databases that get used in mission critical  IT systems. In some cases entire systems being build on top of open source  foundations. Since we have been benchmarking IT software for years, we thought  we would set our sights on some of the most commonly used open source software  (OSS) projects. Quality of Open Source Software Projects Report
Technical debt can arise from many places and today we will focus on poorly used and created feature flags.
Feature Flags: Good, Bad, or Both?
Technical debt starts off from building fast and making a slew of decisions based on short-term needs that are detrimental to your products long-term stability and maintainability.
Technical Debt: What is it and What to do When You Have it?

Earlier this month, CAST held its annual customer and partner conference in Munich, Germany.

IT and business executives from the Insurance, Banking, Telco and IT Consulting sectors shared how they are working with CAST and why software measurement is critical to the success of their IT projects.

CAST Celebrates 25 Years of Customer Success at Oktoberfest in Munich
In our 29-criteria evaluation of the static application security testing (SAST)  market, we identified the 10 most significant vendors — CAST, CA Veracode,  Checkmarx, IBM, Micro Focus, Parasoft, Rogue Wave Software, SiteLock,  SonarSource, and Synopsys — and researched, analyzed, and scored them. This  report shows how each measures up and helps security professionals make the  right choice. Forrester Wave: Static Application Security Testing, Q4 2017  Analyst Paper
Here, at On Technical Debt, we often discuss the difficulties of communicating technical debt to business stakeholders, the consequences that arise from it, and the ways to about paying it back - but in this post we are going  to focus on why it is there to begin with.
The "Why" of Technical Debt

It’s no question that Cloud is no longer a passing phase. In the span of a few years, Cloud has moved from an interesting concept to a useful business tool. What began as a creative tool for testing has moved into the mainstream as a way to improve hardware utilization and expand capacity. The benefits for Cloud are well established, and more customers are moving to consumption-based models, either with captive or public Cloud solutions. Many tools exist to help with Cloud migrations, but few have the flexibility to “see through the Cloud” to the application code, and make that code fit this new world.

See Through the Cloud!
This study by CAST reveals potential reasons for poor software quality that  puts businesses at risk, including clashes with management and little  understanding of system architecture. What Motivates Today’s Top Performing  Developers Survey
This summer Southwest Airlines underwent various technical failures that led to the cancellation of 2,300 flights over the span of four days. This cost the airline approximately $54 million.
How to Avoid Technical Failure by Recognizing the Consequences of Technical Debt
Remodeling software should be done in the same mindset under which we remodel a house: to make it last longer and run better. Companies should be invested in mending their code to be able to get more productivity out of it.
Stop Paying Back Technical Debt, Accumulate Technical Wealth
The project triangle is a well known model to many, even the most junior of software developers know it.
Is The Technical Debt Metaphor Actually Helpful?

This blog is from CAST’s keynote speech at MeGSuS’16, 3rd International Workshop on Measurement and Metrics for Green and Sustainable Software. Download the presentation here.

Fueled by our growing thirst for constant connectivity and the dawn of the Internet of Things, the energy required to power all the world’s computers, data storage and communications networks is expected to double by 2020 according to the latest research by McKinsey & Company. This would increase the total impact of IT technology, in terms of global carbon emissions, by at least 3%.

Green Indexes Used in CAST to Measure Energy Consumption of Code
This is a great post from the Software Engineering Institute on early software defect detections with technical debt.
Detecting Software Vulnerabilities with Technical Debt
When it come to the struggles of undergoing digital transformation, many organizations are going about their digital transformation though a bimodal approach, and according to this post, this is unsustainable.
Integrating Innovation and Legacy Systems: Reducing Technical Debt in Digital Transformation