Examples of using Technical debt in English and their translations into Portuguese
{-}
-
Colloquial
-
Official
-
Medicine
-
Financial
-
Ecclesiastic
-
Ecclesiastic
-
Computer
-
Official/political
The process instantiation is supported by a tool based on a protocol and registration of technical debt items using a defined catalog,
Learn how to shed your technical debt and save money for more innovation by modernizing your data center with next-generation converged systems,
for the studied teams, to discuss technical debt in their daily work,
This dissertation focus on measuring methods of technical debt and a literature review has showed a division in the works already done according to the approach used,
this research has as main objective to define a technical debt management model, taking in consideration
phenomenon which ward cunningham called¿technical debt¿as a metaphor to financial debt. .
under budget without accumulating a great deal of technical debt.
actively help you reduce technical debt and extend the longevity of your code base.
For example, it is important to have very few bugs in the product and little to no technical debt, but you can't stop developing new features completely if you want to survive in such a dynamic market.
Investigating the causes of software technical debt at the architectural level.
This technical debt makes it difficult to improve the process.
Alleviate technical debt with a practical path.
Later on he continued his keynote talking about Technical Debt.
The metaphor of technical debt was coined by cunningham
Technical debt(td) is a metaphor that describes the effect of immature artifacts in software development.
They need to make it clear that they value quality vs. all out speed and the accumulation of technical debt.
This helps eliminate technical debt Updater- Displays upgrade alerts upon launch in the console.
Michael Jenkins: There are two main problems with legacy processes: technical debt and manual work.
Lowe notes that not coding a technical debt in the first place is easier than removing it later.
Products with monolithic architectures, technical debt, and few automated tests might have a slower increase in deployment frequency,
