-
A stab at another VPS
Several weeks ago, the VPS (virtual private server) that I use to host my blog and Web site went down for more than 6 hours. The service, like most VPS services, has a 99%+ uptime guarantee. Well, the uptime guarantee is kind of useless as the site is still down and the few bucks credit I got aren't really worth much. Their support folks didn't get back to me until the end of the outage and then gave some excuse that they were short staffed. By the time the site had come back up, I had already signed up with another VPS and restored my site (I have scripts on the VPS that backup nightly and then everyday, my Mac syncs down the backups). The whole setup process takes me about 2 hours as my VPS isn't all that complicated.
-
My new office
Yesterday, my wife asked if I wanted to come with her to pick up our son that was spending the day at my parents. I asked her what time and she said that she'd leave around 4pm. Hmmm, I had a 4 pm meeting. I said "sure", but she'd have to drive. 4 pm came around, I got on my phone call, turned on my Sprint MiFi, switched my Mac over to the MiFi's network and was all set.
-
Leaving logging statements in production code
I've written in the past about how I think that leaving logging code in production or release builds is bad practice. While I have no objections to being able to turn debug logging on or off to help troubleshoot problems in the field, it shouldn't be on by default. Recently I've read conflicting views about leaving NSLog statements in code. One really good solution is:
-
Tenets of software development
Lately I've been talking to people about some development projects and I keep repeating my 2 tenets of software development. The first is from Brian Hall of Mark/Space. He used to say