Sunday, February 28, 2016

Recommended Reading

Josh Marshall from TPM read the same Times article I linked to yesterday about the GOP struggling to control the Trump monster it unchained, and he has some thoughts of his own that are very applicable:
If we do a project in a rough and ready way, which is often what we can manage under the time and budget constraints we face, we will build up a "debt" we'll eventually have to pay back. Basically, if we do it fast, we'll later have to go back and rework or even replace the code to make it robust enough for the long haul, interoperate with other code that runs our site or simply be truly functional as opposed just barely doing what we need it to. There's no right or wrong answer; it's simply a management challenge to know when to lean one way or the other. But if you build up too much of this debt the problem can start to grow not in a linear but an exponential fashion, until the system begins to cave in on itself with internal decay, breakdowns of interoperability and emergent failures which grow from both.  
This is a fairly good description of what the media is now wrongly defining as the GOP's 'Trump problem', only in this case the problem isn't programming debt. It's a build up of what we might call 'hate debt' and 'nonsense debt' that has been growing up for years.
Read the rest here.

No comments: