Главная
Study mode:
on
1
Introduction
2
Agenda
3
Clean code
4
Martin Fowler
5
Why the quadrant
6
Status quo
7
Do you have technical debt
8
Application level
9
Whos responsible
10
What to do
11
I dont care
12
Measuring technical debt
13
The Boy Scout rule
14
Pick it up
15
Approaching legacy applications
16
Code reviews
17
Team communication
18
How to avoid technical depth
19
Coverage
20
Architecture
Description:
Explore the concept of technical debt in software development through this insightful EuroPython 2016 conference talk. Delve into the pervasive nature of technical debt across service and product-oriented businesses, examining its inevitability and potential prevention strategies. Understand the distinction between technical debt and its associated interest, analyzing their qualifications and management approaches. Investigate the various levels at which debt and interest manifest in projects, and consider whether technical debt is truly unavoidable. Learn about clean code principles, Martin Fowler's perspectives, and strategies for identifying and addressing technical debt. Discover methods for measuring technical debt, implementing the Boy Scout rule, and approaching legacy applications. Gain insights into effective code reviews, team communication, and techniques for avoiding technical debt accumulation. Cover topics such as code coverage, architecture, and their roles in managing technical debt throughout the software development lifecycle. Read more

Managing Technical Debt

EuroPython Conference
Add to list