Technical debt, a burden for technology companies: a study shows that computer scientists lose almost a day of work a week to solve them
Around six hours a week are spent by IT professionals correcting errors and deficiencies in what are known as technical debts, according to the State of Technical Debt 2021 study by technology firm Stepsize. In other words, they lose almost one day of work per week to solve problems resulting from poor code.
Technical debt is a concept used in development to define the cost of maintaining and fixing poorly built software, often because it was built too quickly or because a good quality control was not carried out before release. The consequence of this is bugs and interruptions in the tool's operation, which means that computer scientists have to intervene to solve them and spend part of their working day repairing instead of developing.
According to the report, technical debt is not only bad for workers' productivity and, therefore, for the company's productivity, but also harms the morale of the team, which has to constantly deal with errors caused by previous bad work.
The text points out that the backend, applications and websites of companies are the parts that usually accumulate the most technical debt.
80% of digital products will be created by people who do not know how to program by 2024, according to Gartner: low-code opens the doors of development
IN XATAKA
80% of digital products will be created by people who don't know how to code by 2024, according to Gartner: low code opens the doors to development
These types of legacy problems not only make it difficult for current tools to function, but can also complicate or even prevent the development of new features, forcing the adoption of very limited solutions.
Despite all this, the report also highlights that, while poor code is an important part of the problem, it is no less important that companies do not have processes in place to manage these technical debts. Sixty-six percent of IT respondents believe that their teams would double their efficiency if their companies had such processes in place.
Technical debt, a burden for technology companies: a study shows that computer scientists lose almost a day of work a week to solve them
Around six hours a week are spent by IT professionals correcting errors and deficiencies in what are known as technical debts, according to the State of Technical Debt 2021 study by technology firm Stepsize. In other words, they lose almost one day of work per week to solve problems resulting from poor code.
Technical debt is a concept used in development to define the cost of maintaining and fixing poorly built software, often because it was built too quickly or because a good quality control was not carried out before release. The consequence of this is bugs and interruptions in the tool's operation, which means that computer scientists have to intervene to solve them and spend part of their working day repairing instead of developing.
According to the report, technical debt is not only bad for workers' productivity and, therefore, for the company's productivity, but also harms the morale of the team, which has to constantly deal with errors caused by previous bad work.
The text points out that the backend, applications and websites of companies are the parts that usually accumulate the most technical debt.
80% of digital products will be created by people who do not know how to program by 2024, according to Gartner: low-code opens the doors of development
IN XATAKA 80% of digital products will be created by people who don't know how to code by 2024, according to Gartner: low code opens the doors to development These types of legacy problems not only make it difficult for current tools to function, but can also complicate or even prevent the development of new features, forcing the adoption of very limited solutions.
Despite all this, the report also highlights that, while poor code is an important part of the problem, it is no less important that companies do not have processes in place to manage these technical debts. Sixty-six percent of IT respondents believe that their teams would double their efficiency if their companies had such processes in place.