Scribd
Upload
105 views42 pages

Technical Debt Latest

This document discusses technical debt in software development. It defines technical debt as additional work required to develop software due to quick and dirty solutions, which incur interest payments in the form of extra effort in future development. Static code analysis and behavioral code analysis are presented as ways to detect technical debt through metrics like code complexity, code coverage, rule violations, change coupling, and code biomarkers. Paying off technical debt requires prioritizing it, allocating time to address it, making it transparent, and communicating it properly at both the team and company levels. The cost of technical debt is the time lost from quick solutions.

Uploaded by

Ramón Antonio Parada
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
Download as pdf or txt
105 views42 pages

Technical Debt Latest

This document discusses technical debt in software development. It defines technical debt as additional work required to develop software due to quick and dirty solutions, which incur interest payments in the form of extra effort in future development. Static code analysis and behavioral code analysis are presented as ways to detect technical debt through metrics like code complexity, code coverage, rule violations, change coupling, and code biomarkers. Paying off technical debt requires prioritizing it, allocating time to address it, making it transparent, and communicating it properly at both the team and company levels. The cost of technical debt is the time lost from quick solutions.

Uploaded by

Ramón Antonio Parada
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
Download as pdf or txt
Download as pdf or txt
You are on page 1/ 42

TECHNICAL DEBT

GURU LEVEL
s
@fernando_ceja
I am Fernando Cejas
I am here because I love to share

Hello!
experiences and disasters I have
made in my professional life.

× Twitter: @fernando_cejas
× Github: @android10
× Blog: fernandocejas.com
“BAD CODE IS
ALWAYS
imprudent”
In an ideal world...every proje
ct...

Clean On
Finished
code budget
on time
Even better… our perfect pro
ject...

Additional Tested ???


features twice
Level
FACT: OUR SOFTWARE
IS TERRIBLE!!!
And that does not make it special.
All software is terrible, and yes, we know
it is definitely TRUE
WHAT IS LEGACY CODE?
Code without tests
Code that someone else has written

Code difficult to change Difficult to understand

ANTI-PATTERNS
No separation of concerns
WHAT IS RECKLESS DEBT?
Code that violates
design principles
Without even a short term payoff
WHAT IS TECHNICAL DEBT?
It is a metaphor
doing things the quick and dirty way sets us up with a
technical debt

Incurs INTEREST PAYMENT


which come in the form of the extra effort that we have
to do in future development because of the quick and
dirty design choice.
Technical debt is the
additional effort and
work REQUIRED to
complete any software
development.
“TEchnical debt
is reflected on
legacy code”
Real case scenario:
ADDING A NEW
FEATURE
THE “EASY”
WAY:
Built up with messy
design and code, will
get you there faster.
THE “HARD”
WAY:
Built up with cleaner
design and code, that
takes a lot more time
“Accept some
technical debt
for tactical
reasons”
DETECTING
TECHNICAL DEBT
Level
STATIC CODE
ANALYSIS
Static CODE ANALYSIS: CODE MET
RICS
Cyclomatic
Code coverage SQALE-rating
complexity A lack of unit tests is a source Broad evaluation of software
complexity of classes and of technical debt. This is the quality. The scale goes from A
methods by analyzing the amount of code covered by to E, with A being the highest
number of functional paths in unit tests. quality.
the code

Number of rule Bug count


violations As technical debt increases,
quality of the software
Number of rules violated from a decreases. The number of bugs
given set of coding will likely grow.
conventions.
Level
TECH DEBT
RADAR
+PAIN

TECH
DI
Login

Data
Layer
Search

DEBT -Dev TIME

Player Photos
+Dev TIME

RADAR
Share

UI
Layer

-PAIN
Level
BEHAVIORAL CO
DE
ANALYSIS
“TEchnical debt
is reflected on
legacy code”
“TEchnical debt
is NOT ONLY
reflected on
legacy code”
BEHAVIORAL CODE ANALYSIS:
1. Consider the organization and people side of the system.

2. This gives you valuable information that is invisible in the


source code itself, such as measures of team autonomy and
off-boarding risks.

3. How developers interact with the code.


behavioral CODE ANALYSIS: MET
RICS
Hotspots Refactoring Targets
Hotspots identify the modules with Prioritize improvements to these files
most development activity -- often since they have the highest technical
technical debt. debt interest rate.

Change coupling Code biomarkers


Change coupling helps us Code Biomarkers aim to indicate
uncover implicit change specific properties at very low code
patterns in our code. level.
EXTRA BALL!!
PAYING
TECHNICAL DEBT
Paying debt at team level:
1. Prioritize and keep track of it.

2. Allocate time to address it.

3. Technical Debt days.


Paying debt at COMPANY level:
1. Educate people about its existence.

2. Make it transparent.

3. Communicate it properly.
Paying debt at COMPANY level:

COST OF DELAY
This (mostly manual) metric helps to make visible
how much time a team loses due to technical
debt.
SOME DAYS YOU CANNOT GET RID
OF A BOMB...
THANKS!
Any questions?
You can find me at @fernando_cejas (twitter) & @android10 (github)
Credits
Special thanks to all the people who made and
released these awesome resources for free:
× Presentation template by SlidesCarnival
× Photographs by Startupstockphotos

You might also like