1. 2

  2. 2

    What the author calls “technical weight” I would call just “complexity”. But this is a good, thorough overview of how software complexity can arise and how to avoid increasing it unnecessarily.

    1. 1

      You beat me to it. I was thinking the phrase “intrinsic complexity” but my memory is broken so I can’t recall if that’s how it’s normally used. I won’t go so far as saying the author is confusing that with technical debt. There probably should be some overlap in these discussions. I might think along the lines of good debt like many companies take on versus bad debt. Or we could just call it something with high overhead to run that’s still essential. Maybe even a loss leader.

      It’s not what we normally talk about in the technical debt discussions. We talk about it under complexity banner all the time. That’s what it really is no matter how we phrase it.