# Reducing Technical Debt by Removing Development Friction

DevFeed: [Reducing Technical Debt by Removing Development Friction](<https://devfeed.tech/articles/fix-like-no-one-s-watching-36164.md>)

Original publisher: [Read original article](<https://overreacted.io/fix-like-no-ones-watching/>)

Published: 2019-02-15T00:00:00Z

Content type: opinion

Language: en

Sources: [Dan Abramov](<https://devfeed.tech/sources/dan-abramov.md>)

Topics: [Code](<https://devfeed.tech/topics/code.md>), [unit tests](<https://devfeed.tech/topics/unit-tests.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>), [bug](<https://devfeed.tech/topics/bug.md>)

Tags: [bug](<https://devfeed.tech/tags/bug.md>), [code](<https://devfeed.tech/tags/code.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [features](<https://devfeed.tech/tags/features.md>), [performance](<https://devfeed.tech/tags/performance.md>), [technical](<https://devfeed.tech/tags/technical.md>), [unit-tests](<https://devfeed.tech/tags/unit-tests.md>)

## AI overview

The article argues that technical debt includes not only visible code problems but also friction that discourages developers from investigating bugs, trusting deployment scripts, locating regressions, or experimenting. It concludes that actively reducing this friction helps prevent important work from being indefinitely postponed.

## Source excerpt

The other kind of technical debt.