Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Technical Debt: Do Managers (Unintentionally) Force Bad Code?

DZone's Guide to

Technical Debt: Do Managers (Unintentionally) Force Bad Code?

· Agile Zone ·
Free Resource

[Latest Guide] Ship faster because you know more, not because you are rushing. Get actionable insights from 7 million commits and 85,000+ software engineers, to increase your team's velocity. Brought to you in partnership with GitPrime.

I still have estimation on the mind. I saw The Impact of Accidental Complexity on Estimates and I was wondering about the effect of management on bad code. Do managers sometimes force developers to write bad code by allowing technical debt? Jay’s third point implicates technical debt as a cause:

Introducing technical debt increases accidental complexity, and as a side-effect invalidates previous estimates and increases the likelihood that future estimates will differ in size drastically.

(Free Estimation Ebook)

Accepting technical debt now buys you time now. It does increase time to pay back the debt later. I wonder if we have any idea how much time it takes later. I bet we underestimate how much time it takes to undo the technical debt.

[Latest Guide] Ship faster because you know more, not because you are rushing. Get actionable insights from 7 million commits and 85,000+ software engineers, to increase your team's velocity. Brought to you in partnership with GitPrime.

Topics:

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}