Technical Debt in Practice

How to Find It and Fix It

Neil Ernst, Julian Delange, Rick Kazman

$85

Paperback

Not in-store but you can order this
How long will it take?

Availability Information

We source books from suppliers in Australia and overseas. For books we don't currently have in stock, the time it takes to get them from our suppliers can vary widely - from a few days to a few months - so we check each book with each supplier to determine the expected time it will take to be supplied to us.

We then advise you accordingly. If the time taken to get any book is too long for you, you can let us know and we will cancel or adjust your order, and refund as required.

To find out the anticipated arrival time for specific items prior to ordering, please contact us by phone or email:

Phone +61 2 9264 3111, or 1800 4 BOOKS (1800 4 26657) if outside Sydney:
option 1 Abbey's Bookshop (Crime, History, Science, Kids & more) • info@abbeys.com.au
option 2 Language Book Centre (ESL & Foreign Languages) • language@abbeys.com.au
option 3 Galaxy Bookshop (Sci-fi, Fantasy, Romance, Graphic Novels) • sf@galaxybooks.com.au

QTY:

English

MIT Press
21 September 2021

Computing: general

The practical implications of technical debt for the entire software lifecycle; with examples and case studies.

The practical implications of technical debt for the entire software lifecycle; with examples and case studies.

Technical debt in software is incurred when developers take shortcuts and make ill-advised technical decisions in the initial phases of a project, only to be confronted with the need for costly and labor-intensive workarounds later. This book offers advice on how to avoid technical debt, how to locate its sources, and how to remove it. It focuses on the practical implications of technical debt for the entire software life cycle, with examples and case studies from companies that range from Boeing to Twitter.

Technical debt is normal; it is part of most iterative development processes. But if debt is ignored, over time it may become unmanageably complex, requiring developers to spend all of their effort fixing bugs, with no time to add new features--and after all, new features are what customers really value. The authors explain how to monitor technical debt, how to measure it, and how and when to pay it down. Broadening the conventional definition of technical debt, they cover requirements debt, implementation debt, testing debt, architecture debt, documentation debt, deployment debt, and social debt. They intersperse technical discussions with ""Voice of the Practitioner"" sidebars that detail real-world experiences with a variety of technical debt issues.

By: Neil Ernst, Julian Delange, Rick Kazman
Imprint: MIT Press
Country of Publication: United States
Dimensions: Height: 229mm, Width: 152mm,
Weight: 368g
ISBN: 9780262542111
ISBN 10: 0262542110
Pages: 288
Publication Date: 21 September 2021
Audience: General/trade , ELT Advanced
Format: Paperback
Publisher's Status: Active

1 Introduction 2 The Importance of Technical Debt 3 Requirements Debt 4 Design and Architecture Debt Case Study A: Brightsquid 5 Implementation Debt 6 Testing Debt Case Study B: Twitter 7 Deployment Debt 8 Documentation Debt Case Study C: Scientific Software 9 Technical Debt in Machine Learning Systems 10 Team Management and Social Debt 11 Making the Business Case 12 Conclusions Appendix--Full Text of Interviews Interview: Marco Bartollini Interview: Julien Danjou Interview: Nicolas Devillard Interview: Vadim Mikhnevych Interview: Andriy Shapochka Index

Neil Ernst is Assistant Professor of Computer Science at the University of Victoria, British Columbia. Julien Delange is Staff Software Engineer at Twitter and Founder of Code Inspector, a technical debt platform analysis. Rick Kazman is Professor in the Department of Information Technology Management at the University of Hawaii and Visiting Researcher at the Software Engineering Institute at Carnegie Mellon University.