Managing Technical Debt: Reducing Friction in Software Development
by Philippe Kruchten, Robert Nord, Ipek Ozkaya
Preface
Philippe: I ran into technical debt long before I had a name for it. In 1980, I was working at Alcatel on some peripheral device, and the code had to fit in 8 kilobytes (kB) of ROM (Read-Only Memory). With the deadline to “burn” the ROMs approaching, we did a lot of damage to the code to make it fit, thinking, “Oh, for the next release we’ll have 16 kB available, we’ll make it right”… We did get 16 kB of ROM for the next release, but we never, ever fixed all the abominable things we had to do to the source code because the deadline for the next product was, again, too close. New programmers coming on board would say, “Wow, this is ugly, brain-damaged, awful. How did you end up writing such bad code?” Colleagues would reply, “Oh, yes, ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access