Is Technical Debt the right metaphor for Continuous Update?

The environmental pressure on software has dramatically changed in few years, both in quality and quantity.
Security is the main force but other dynamics can be seen, the adoption of agile, shortest product cycles, and more. As a consequence the software is no more written once and run many times: it must be updated continuously.
If we, as an industry, continue to use the classic category of Technical Debt, IT will be crushed by the forces at hand, pulling the business side along. I propose to introduce a new term for this phenomenon: Technical Inflation. It is not simply to mark the difference but to help discuss and explain to other stakeholders what is happening on the technical side and the effect on the entire business. The new perspective impacts how we plan and budget, how we manage changes and automation, and the need to excel on engineering to save the bottom line.

Giulio Vian

Principal DevOps Engineer

Carlow, Ireland


Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.

Jump to top