For the past month or so I’ve been running close to the office. It’s a short run on Corporate Center Drive from US 54 to Trinity Road. I estimated it at about 1 mile, and I am running the round-trip twice.
Today, I’ve finally used gmap-pedometer to measure the distance. It was very close: 0.97 miles. That makes my run about 3.9 miles long.
The only impressive thing is the elevation on that 1-mile run: almost 90ft of vertical elevation. No wonder the run seemed longer.
I’ve read some recent posts about how cool gnucash is, and decided to give it a try. This is the second time I try to use it, hopefully this time I’ll stick with it.
My first experience was “interesting but too buggy”. That was probably a good 2 years ago. Ever since, it has come along nicely. Last night it did not crash on me, not even once. It handled both *.qif and *.qfx files, I used the files downloaded from my accounts (bank). I know I’m not supposed to do that, normally one would keep records of the expenses and would reconcile against the statement – downloading the transaction from the bank will not make sure the bank hasn’t mistakenly messed something up. But I needed some data.
Once I had the data imported, I started to assign it to various gnucash “accounts”, and I got hooked when I saw how easy it is to see how much you paid the cable company etc.
Although it got to be pretty late in the night, I decided to give scheduled transactions a try too – that was one of my biggest worries with gnucash. I used to keep my finances in a gnumeric spreadsheet (I did converted it to .xls at some point so I can read it with OpenOffice if I had too – even though gnumeric is supposed to handle the Open Document Format too). Every month I would copy the block of transactions from the previous month, manually change the dates, keep only the transactions I knew about etc. As it turns out, gnucash will do the scheduling for you automatically (you do have to choose between having the transactions created automatically for you some number of days in advance or be prompted when such a transaction is created).
Around 2AM I finally decided to go to bed, after being pleasantly surprised and very committed to switch away from the spreadsheet.
Whether I will really input all the receipts in the system and reconcile with the credit card statement or just mark the payments from the checking account into the liabilities/credit card account, that’s to be determined – I think it would make sense to spend the effort of tracking down the receipts, I’d be curious to know how many errors the banks made in my credit card statements. If you think it’s not possible, think again: it happened twice so far to have a check debited by the bank with $5 or $10 extra, even if the other side got the proper amount. I caught those errors because they were in my checking account, but I am not that rigorous with my credit cards – if I recognized the transaction it was good enough for me, I wasn’t checking the amount very carefully at all.
After a gorgeous Saturday, with temperatures close to 80, the Sunday didn’t look promising: rainy and cold. But, just like the last time, the rain stopped around noon, just in time for the start.
I could not leave the church until 1:30PM, which meant I was only able to start around 1:50. I was nervous I won’t be able to finish a green course, but Nadya (the course director) encouraged me to do it anyway. And I am happy I did.
This is the result. I timed myself too (I kept the splits for each control), but I refused to look at the total time. I thought I will be back in less than an hour, I was very surprised and disappointed at the finish line that I was 23 minutes over an hour (15 minutes after the 3PM closing time). I don’t exactly know why I thought I did it faster, I did try to run all the way through. The course was beautiful, it also helped that I started to know Umstead South a bit better and some controls were a deja-vu (especially control 7 on the cliff, but also the steep river bank, control 8 – I am positive we’ve had controls there before – it’s easy to find out since I have the maps for the past 2 years). (update: those were controls 40 and 53 from the Umstead 911 Score Event)
Other surprises: Green course was 5.6km, it’s usually 5.1km; for the first time I notice there was a Blue course as well (8.7km) – not that I could do it in the timeframe I had, plus it would definitely be long. Nadya estimated 10 minutes per kilometer in orienteering, I seem to be at 15.
On the way back home I noticed how gorgeous the woods are in the fall. It’s probably the best month to do orienteering, cool enough and with less vegetation, plus the foilage.