Phew!
The new year brought with it a new job, new apartment, and new car. As a result of the former 2 I was completely in the weeds with any projects like this service. Thankfully it runs on its own however being in the weeds meant nearly 100 key requests sat unanswered. Part of the problem was how I input the data to the DB. It was anything but graceful.
A friend of mine has been coaching me to learn Ruby for some very specific reasons (so please don’t tell me I should learn some other language). I took the opportunity to write a script that will speed up the data entry and parsing. After actually successfully doing that I was able to plow through the pending requests.
The new car means I haven’t been taking Caltrain for the last several months. This is in part because I’m no longer within a reasonable biking distance to 4th/King and I would have to either bike from Mountain View or take VTA to my new office. I have a rule that excluding walking I will not take more than 3 modes of transportation to work. That said I need to really need to figure out timing to drive to Millbrae (with or without my bike) and take Caltrain to Mountain View where I either bike or take VTA. but of course Caltrain has been about as reliable as MUNI so I’ve scrapped the whole idea of taking Caltrain all together for the time being. I’d really like to use it again as I’d be gaining at least 1h30m of work time.
Anyhow things are back on track and its a good thing too because Twitter is discontinuing support for basic authentication. That means unless I get moving it will outright break. I better get cracking!
Thanks again to everyone who continues to make the service the success that it is.
Leave a Reply