Pulse en una miniatura para ir a Google Books.
Cargando... Managing Technical Debt: Reducing Friction in Software Development (Sei Series in Software Engineering)por Philippe Kruchten
Ninguno Cargando...
Inscríbete en LibraryThing para averiguar si este libro te gustará. Actualmente no hay Conversaciones sobre este libro. sin reseñas | añadir una reseña
“This is an incredibly wise and useful book. The authors have considerable real-world experience in delivering quality systems that matter, and their expertise shines through in these pages. Here you will learn what technical debt is, what is it not, how to manage it, and how to pay it down in responsible ways. This is a book I wish I had when I was just beginning my career. The authors present a myriad of case studies, born from years of experience, and offer a multitude of actionable insights for how to apply it to your project.” –Grady Booch, IBM Fellow Master Best Practices for Managing Technical Debt to Promote Software Quality and Productivity As software systems mature, earlier design or code decisions made in the context of budget or schedule constraints increasingly impede evolution and innovation. This phenomenon is called technical debt, and practical solutions exist. In Managing Technical Debt , three leading experts introduce integrated, empirically developed principles and practices that any software professional can use to gain control of technical debt in any software system. Using real-life examples, the authors explain the forms of technical debt that afflict software-intensive systems, their root causes, and their impacts. They introduce proven approaches for identifying and assessing specific sources of technical debt, limiting new debt, and “paying off” debt over time. They describe how to establish managing technical debt as a core software engineering practice in your organization. Discover how technical debt damages manageability, quality, productivity, and morale–and what you can do about it Clarify root causes of debt, including the linked roles of business goals, source code, architecture, testing, and infrastructure Identify technical debt items, and analyze their costs so you can prioritize action Choose the right solution for each technical debt item: eliminate, reduce, or mitigate Integrate software engineering practices that minimize new debt Managing Technical Debt will be a valuable resource for every software professional who wants to accelerate innovation in existing systems, or build new systems that will be easier to maintain and evolve. No se han encontrado descripciones de biblioteca. |
Debates activosNinguno
Google Books — Cargando... GénerosClasificación de la Biblioteca del CongresoValoraciónPromedio:
¿Eres tú?Conviértete en un Autor de LibraryThing. |
These three authors explore these themes in depth in this work in the field of software engineering. It’s not necessarily a fun topic, but it’s one that any experienced software developer can relate to. The central metaphor of debt repayment also provides a concept that is relatable to the business-people around software. Jumping from new feature to new feature without addressing issues of architecture has a cost, and this book explicates a language and a framework to deal with it more effectively.
The book explores nine principles about technical debt. Each one of these seems basic, yet they explain a more profound point.
1. Technical debt reifies an abstract concept.
2. If you do not incur any form of interest, then you probably do not have actual technical debt.
3. All systems have technical debt.
4. Technical debt must trace to the system.
5. Technical debt is not synonymous with bad quality.
6. Architecture technical debt has the highest cost of ownership.
7. All code matters!
8. Technical debt has no absolute measure—neither for principal nor interest.
9. Technical debt depends on the future evolution of the system.
This topic is not sexy (and I don’t know of any topic termed “debt” that would be considered “sexy”). Nonetheless, this book provides specific ways to tackle the debt and to raise awareness of these concepts in software teams. Reading an in-depth analysis on this topic is necessary for all software developers who aim to achieve mastery of their craft. This book will certainly help them take such a step. ( )