1. 8
  1.  

  2. 5

    In the Google thread, we discussed the problem that there wasn’t any measurement of or value seen in eliminating technical debt. A few agreed that this was a problem leading to the kind of bad software we see today. I figured you all might like this article since it was the best attempt I saw at doing the opposite: accounting for technical debt in a way that managers can see and might choose to act on. For good measure, here is another blog post that lists some negatives developers or project managers can mention when trying to sell upper management on preventing or removing technical debt.

    1. 2

      It’s good to see these parasites are doing something with the $16 fee they charged on top of a $25 ticket I bought.

      1. 2

        Are you flaming for the sake of flaming?