Prioritizing Technical Debt as if Time & Money Matters • Adam Tornhill • GOTO 2019
Channel:GOTO Conferences · Length:44:46 · Published:2019-12-13 · Views:56433
Summary
Adam Tornhill's GOTO Copenhagen 2019 talk on how to prioritize technical debt in large codebases. It argues for combining code complexity with change frequency (hotspots) from version control data, rather than trying to quantify debt in the abstract.
Why HN recommends it
Cited as a practical approach to finding the technical debt that matters, and as a reference for codebase visualization.
I think Adam Tornhill has a nice take on this. — HN, 2021
Software architecture & design · Testing, debugging & developer tools · Software practice, open source & careers
Subtitles (excerpt)
[Music] so good morning everyone and welcome to this session on prioritizing technical depth this is a broad topic and I have a lot of stuff to cover for you today so I want us to jump right in and start by covering the forces we have to balance when building large-scale software systems and I do think that these forces are wery well captured in something called Lehman's loss of soft revolution so let me ask you how many of you have heard about Lehman's loss not so many that's good I got something new for you it's perfect so Lehman's law they are pretty fascinating because they are old they were written down in 1970s early 1980s and they are not that well known so I tried to do my best to popularize them and today I want to show just two of those laws to you here now so let's start with the first law and see if it resonates with your experience so the first law of software evolution is the law of continuous change will Lehman says that the system has to continuously evolve and adapt or it will become progressively less useful over time do you recognize this yeah this is the right reason where we keep adding new stuff new features to existing products because we need to keep them relevant we need to respond to competitors and
On Hacker News
I think Adam Tornhill has a nice take on this. He recommends tech debt not be quantified as such, but encourages focusing on areas with high complexity and large churn GOTO 2019 • Prioritizing Technical Debt as if Time and Money Matters • Adam Tornhill [VIDEO] — clumsysmurf, 2021-01
principlkes of chaos engineering : [LINK] unix as an ide : [LINK] using ed : [LINK] editor articles : [LINK] pioritizing technical debt : [VIDEO] — sargstuff, 2022-12
That's a great visual presentation, but not really an innovation. The CodeScene tool has that built in together with a set of deep analyses on top (see [LINK] ). There are several public conference talks that cover this visualization and related use cases: [VIDEO] — nephrenka, 2021-08
Related videos
- RailsConf 2014 - All the Little Things by Sandi Metz · Confreaks · 38:47
- "Simple Made Easy" - Rich Hickey (2011) · Strange Loop Conference · 1:01:38
- "Making Impossible States Impossible" by Richard Feldman · elm-conf · 25:06
- "Testing Distributed Systems w/ Deterministic Simulation" by Will Wilson · Strange Loop Conference · 40:20
- 🚀 TDD, Where Did It All Go Wrong (Ian Cooper) · DevTernity Conference · 1:03:55
- Bret Victor - Inventing on Principle · Rui Oliveira · 54:20
- How To Design A Good API and Why it Matters · Google TechTalks · 1:00:19
- The Value of Values with Rich Hickey · InfoQ · 31:43
- Bret Victor The Future of Programming · Joey Reid · 32:55
- Overwatch Gameplay Architecture and Netcode · GDC Festival of Gaming · 1:04:03
- Solving Problems the Clojure Way - Rafal Dittwald · Clojure/north · 1:02:26
- Lecture 1A: Overview and Introduction to Lisp · MIT OpenCourseWare · 1:12:55
- Debugging Under Fire: Keep your Head when Systems have Lost their Mind • Bryan Cantrill • GOTO 2017 · GOTO Conferences · 52:34
- "Performance Matters" by Emery Berger · Strange Loop Conference · 42:15
- Alan Kay - Normal Considered Harmful · powerfuloutlet · 1:07:26
- A Philosophy of Software Design | John Ousterhout | Talks at Google · Talks at Google · 1:01:40