You're reading from Refactoring with C#

Product type Book

Published in Nov 2023

Publisher Packt

ISBN-13 9781835089989

Pages 434 pages

Edition 1st Edition

Languages

Concepts

Programming Language

Author (1):

Matt Eland

Table of Contents (24) Chapters

Preface

1. Part 1: Refactoring with C# in Visual Studio

2. Chapter 1: Technical Debt, Code Smells, and Refactoring

3. Chapter 2: Introduction to Refactoring

4. Chapter 3: Refactoring Code Flow and Iteration

5. Chapter 4: Refactoring at the Method Level

6. Chapter 5: Object-Oriented Refactoring

7. Part 2: Refactoring Safely

8. Chapter 6: Unit Testing

9. Chapter 7: Test-Driven Development

10. Chapter 8: Avoiding Code Anti-Patterns with SOLID

11. Chapter 9: Advanced Unit Testing

12. Chapter 10: Defensive Coding Techniques

13. Part 3: Advanced Refactoring with AI and Code Analysis

14. Chapter 11: AI-Assisted Refactoring with GitHub Copilot

15. Chapter 12: Code Analysis in Visual Studio

16. Chapter 13: Creating a Roslyn Analyzer

17. Chapter 14: Refactoring Code with Roslyn Analyzers

18. Part 4: Refactoring in the Enterprise

19. Chapter 15: Communicating Technical Debt

20. Chapter 16: Adopting Code Standards

21. Chapter 17: Agile Refactoring

22. Index

Why subscribe?

23. Other Books You May Enjoy

Communicating technical debt

Explaining technical debt to non-developers can be challenging. Even when management trusts the development team, it is difficult for managers to understand what engineers deal with or how technical debt slows the software engineering process and introduces tremendous quality risks whenever the application is changed.

Technical debt as risk

In the course of my career, I’ve learned that while management has trouble understanding technical debt, there’s something they have a much better understanding of: risk.

This may sound strange, but I’ve found the best way to help management understand technical debt is to present it in terms of risk management.

Every aspect of technical debt in your system has both a probability and an impact.

The probability of a piece of technical debt is the likelihood that the piece of technical debt will impact the development team during development or when the application is running in production...