Is Technical Debt Equivalent to Malpractice?

27min Snip

00:00

Play full episode

Summary

Transcript

Episode notes

The hosts discuss the concept of technical debt and whether it should be equated to malpractice. They explore the analogy between financial debt and tech debt, highlighting the importance of responsible software development practices and documentation. The chapter delves into the challenges of communication and knowledge transfer in the tech industry, emphasizing the need for accountability and proper organization of information.

Go Time panelist (and semi-professional unpopular opinion maker) Kris Brandow joins us to discuss his deep-dive on the waterfall paper, his dislike of the “tech debt” analogy, why documentation matters so much & how everything is a distributed system.

Leave us a comment

Changelog++ members support our work, get closer to the metal, and make the ads disappear. Join today!

Sponsors:

Fastly – Our bandwidth partner. Fastly powers fast, secure, and scalable digital experiences. Move beyond your content delivery network to their powerful edge cloud platform. Learn more at fastly.com
Fly.io – The home of Changelog.com — Deploy your apps and databases close to your users. In minutes you can run your Ruby, Go, Node, Deno, Python, or Elixir app (and databases!) all over the world. No ops required. Learn more at fly.io/changelog and check out the speedrun in their docs.
Typesense – Lightning fast, globally distributed Search-as-a-Service that runs in memory. You literally can’t get any faster!

Featuring: