Главная
Study mode:
on
1
Intro
2
Lehman's "laws" of software evolution
3
Technical debt
4
Case study: Prioritizing technical debt
5
Can we measure "code complexity"?
6
Technical debt & people
7
Case study: How quickly can you turn your current codebase into legacy code?
8
Resources
Description:
Explore strategies for prioritizing technical debt in large-scale software systems through this insightful conference talk. Learn how to balance improving existing code with adding new features, and discover techniques for measuring long-term trends in technical debt. Delve into real-world case studies from codebases like Android, Linux Kernel, and .Net Core Runtime to gain a new perspective on software development. Uncover methods to mine version-control data for insights into development organization behavior and patterns. Gain practical knowledge on measuring code complexity, understanding the relationship between technical debt and people, and assessing how quickly a codebase can become legacy. Leave with actionable approaches to make informed decisions about code improvements and maintain a healthy balance between short-term and long-term development goals.

Prioritizing Technical Debt as If Time and Money Matters

GOTO Conferences
Add to list
0:00 / 0:00