I spent some downtime on the train over the last couple of weeks entering numbers into Excel to see where our energy dollars have been going over the last number of years. I have paper statements up until 2010, which is where I stopped (in preparation for scanning and shredding), and I put in our charges for electricity, gas, and the average temperature as provided by BGE. Natural gas prices in the winter have been the biggest cost by far; electricity goes up as we run A/C units but overall it doesn’t see the same peaks and valleys as natural gas.
The downward trend in 2010 is interesting, and I’d like to see where that goes if I add data from 2011 onward, or if it’s an anomaly of some kind. Guess I’ve got to see if BGE will let me download bills from that far backwards or not…
I loaded Yosemite onto my work laptop yesterday morning, figuring it would make a great test case for the rest of the machines I run (my home laptop, Jen’s laptop, a workstation under my desk, client machines, etc.) and overall it’s pretty nice. My work laptop is a Retina 13″ with an SSD, so installation took about 10 minutes and everything looks wonderful. It seems to be fast, there’s no performance hit with anything I can see, and all my apps seem to be running just fine (Adobe Creative Cloud, CS6, Office 2011, and a handful of utility apps I depend upon). The real test will be the aforementioned laptops–my home machine is an early 2010 model MacBook Pro which might not like as many of the visual improvements in Yosemite.
Amazon delivered my copy of Information is Beautiful this morning, and I can testify, it is, indeed, beautiful. An entire book of charts, graphs, and visuals well-designed and displayed, about a huge range of subjects. Go to the site, absorb some of the work, and buy the book. It’s well worth the money.
Monday night I went out to the garage and started running wire to the ceiling for overhead lighting. Currently it’s a mishmash of plugin fluorescent fixtures scrounged from my old job run off extension cords, and I’ve dreamed of simply having a switch next to the door to light the space since we moved in. I ran wire from the panel to a new switchbox near the door and then started fishing wire up to the ceiling, then stopped because I wanted to make sure I was running the wire correctly. It’s looking like I’m on the right track based on this diagram, so I’ll continue getting things in place in preparation for buying the fixtures and a new breaker.
I shot another video interview this week at work, in less than optimal conditions (about 3 hours of advance notice, overcast weather) and it turned out pretty well. I’m getting the video portion dialed in, having practiced a lot on my own and helping my friend Dave shoot an event last week. The audio is the thing that’s bugging me. I’ve got the subjects miked up correctly, feeding into a high-quality recorder, but the results aren’t what I was expecting.
The audio I got today was low quality. So bad, in fact, that I was afraid I’d made a technical mistake and was pulling the audio in from the built-in mic on the recorder and not the lav mic on my subject. (In order to boost recording levels on the Zoom H4N, you have to select the input device before changes will stick, and I was afraid I’d switched the inputs). I futzed with the levels in Final Cut Pro but didn’t like the results, and brought the original clip into Audacity to boost the levels, clean the garbage out, and split the signal. Once I’d done that the results were much cleaner and I was ready to sync it to video.
So, I’ve got to run some tests on my recorders to see what the issue is. I have a Roland R-09 as a backup, so I’m going to do a 1-1 comparison on recording levels to see what’s what.
I got an email a couple of days ago about my Flickr Pro account. It’s time to renew my account, which is fine; I’ve been a member for nine years and I’m very happy overall with Flickr as a service. In years past I’ve been able to renew it with no problem, but 2014 is different. Apparently they’ve gone to some kind of “wallet” construct for their payment services, which means they want to store your payment information (um…OK) and tie it to your account. Mind you, this is a Flickr wallet. Here’s the issue: There’s no way to apply my card to the bill. When I enter my card information (correctly) into the wallet, I get the cryptic message: “There was an error.”
So, tell me what I’m supposed to do, Yahoo. Do I put my credit card in again? (Did that. Twice. Didn’t work).
Do I click on the Order History links? (they don’t do a fucking thing).
Do I go to Yahoo and log in there and attempt to find my billing information and clear it up there? (Ha, that’s a goddamn joke. I can barely find the “Log In” button, let alone any billing information. And when I did find a link to the billing page, after a goddamn Google search, they had all my old invoices but not the new one).
Here are a couple of entry-level, UI 101, common sense suggestions to the wizards at Yahoo:
- When there’s an error, tell me clearly what the problem is.
- Don’t fuck with best practices, especially when it comes to important stuff like payments.
- Give me some information about what I can do to fix it so that I can give you my money.
So I have to call someone and sit on hold and try to clear it up tomorrow. Stupid fucks.
The site was up and down intermittently late this weekend for reasons I still haven’t been able to understand. At first I’d get either a timeout or a page that only contained
<html> <head> </head> </html>
Which is about as helpful as a blank sheet of paper. I was able to connect via FTP with no problem and looked over the file structure, but found no problems, so I turned off all WordPress’ plugins and changed the theme back to the default, with no change in status. After replacing the database via phpMyAdmin, I still got nothing, so I contacted the support team and waited. After several hours I got bumped up to tier 2 support, and a man wrote to me in broken English that he couldn’t figure out what was wrong, but restarted HTTP service, and suggested I look on my end. Magically, the site came back up at some point after that. I have no idea what was wrong, but my desire to leave that hosting provider and move to my favored company has gotten ever stronger.
I’ve been using a plugin called WordPress Database Backup, which saves a SQL dump of the database and gives you the choice of emailing it, saving it to the server, or downloading it directly to your computer. I’ve got it emailing to our server weekly, and it’s come in very handy at times like this. I’ve also got three other sites I maintain backing up the same way–just in case. As for site files, I’ve got an Automator script running a weekly file synchronization via Transmit, which keeps everything up to date.