Published Sep 1, 2023

You call it tech debt I call it malpractice

Kris Brandow critically examines the implications of neglecting software documentation and challenges the notion of technical debt as mere oversight, advocating for early integration of archivist roles and better accountability in engineering practices to enhance understanding of distributed systems and improve software outcomes.

Episode Highlights

Topics covered

Episode Highlights

Related Episodes

Good tech debt
Answers 383 questions
Product development structures as systems
Answers 383 questions
The 10x developer myth
Answers 383 questions
Why smart engineers write bad code
Answers 383 questions
Building actually maintainable software ♻️
Answers 383 questions
With great power comes great responsibility
Answers 383 questions
AI makes tech debt more expensive (News)
Answers 383 questions
Computer Science without a computer
Answers 383 questions
From Chef to System Initiative (Friends)
Answers 383 questions
Practices of reliable software design (News)
Answers 383 questions
Complex systems & second-order effects
Answers 383 questions
Back to Agile's basics
Answers 383 questions
Prioritizing tech debt, UI components to copy/paste, learnings from 20 years in software, git-sim & jqjq
Answers 383 questions
The code, prose & conversations that shaped 2023
Answers 383 questions
Stacked diffs for fast-moving code review
Answers 383 questions

Dexa/The Changelog

You call it tech debt I call it malpractice

Topics covered

Popular Clips

Building Computer Systems

The Rush to Build

Decision Documentation Dance

Understanding Distributed Systems

Embracing Ambition

Exploring PCIe Distributedness

Articulating Technical Debt

Rethinking Software Engineering

Rethinking Tech Debt

The Importance of Organizing Information

Unpopular Opinions

The Importance of Information Organization

The Value of Worthless Code

Documenting Software

The Need for Rigor

Episode Highlights

Software Documentation Importance

Distributed Systems Challenges

Tech Debt Critique

Related Episodes

Good tech debt

Product development structures as systems

The 10x developer myth

Why smart engineers write bad code

Building actually maintainable software ♻️

With great power comes great responsibility

AI makes tech debt more expensive (News)

Computer Science without a computer

From Chef to System Initiative (Friends)

Practices of reliable software design (News)

Complex systems & second-order effects

Back to Agile's basics

Prioritizing tech debt, UI components to copy/paste, learnings from 20 years in software, git-sim & jqjq

The code, prose & conversations that shaped 2023

Stacked diffs for fast-moving code review

You call it tech debt I call it malpractice

Topics covered

Popular Clips

Episode Highlights

Software Documentation Importance

Distributed Systems ChallengesKris Brandow explores the pervasive nature of distributed systems, revealing their presence in everyday computing tasks. He discusses the challenges in understanding these systems and the importance of making them accessible to a broader audience.

Distributed Systems Challenges

Tech Debt CritiqueKris Brandow challenges the conventional view of technical debt, suggesting it often masks what should be considered malpractice in software development. He advocates for better documentation and accountability to improve engineering practices and outcomes.

Tech Debt Critique

Related Episodes