Don't Back Down

April 2013

  • How Far Do We Go to Protect Our Own Assets?

    In this case, let's look at the upcoming (in progress?) merger between American and USAirways as an example. Each airline operates a reasonable number of flights at a number of airports across the country. But with nine hubs in this merge, someone is bound to lose. The problem…

  • Paying the Occupy Protesters? Really?

    First came the news that New York City would be paying the Occupy Wall Street protesters more than $100,000 for property damaged when their "camp" was cleared out. Then it was bumped to $230,4000. Seriously? I'm the first to admit that I don't get it. I'mold. On the…

  • Coming to Grips with Insecurity

    Slightly more than eleven years ago – and a bit less than six months after the attacks of September 11, 2001 – I wrote a short piece to no one in particular. I actually addressed it to "Mr. President", at the time meaning it would have been delivered…

  • Continuity Matters in Applications, Too

    A few days ago, I discussed the importance of continuity – generally as it related to movies and television. But continuity is important in applications, too – perhaps even more so. Let's take a look at LinkedIn as one example. For a long time, LinkedIn has offered recommendations,…

  • Disable License Logging Service in SBS 2003

    There is a (somewhat outdated) SBS 2003 server on our network, and as we have discovered, the License Logging Service keeps wanting to restart. It is generally not possible to stop it for any length of time. Even disabling it doesn't work – it keeps coming back on….

  • Why is Everything so Complicated?

    Enough talk about government. Instead, let's look at software. Specifically, why does it have to be so dang complicated? Take updates. It has become fairly commonplace to get them. If you use Windows, there is even a utility helpfully called Windows Update. On a regular basis, it provides…