When I added my recent tweets to this website, I knew Twitter’s 1.0 API was deprecated and I would need to find a solution by mid-March that didn’t require embedding my Twitter OAuth credentials in client-side code. Node.js and Heroku to the rescue…
Continue reading “Fetching Tweets with Node.js and Heroku”
Someone has probably called this out before, but I was browsing through the Daring Fireball archive and found a tasty bit of claim chowder regarding the likelihood of Apple adding Exchange support to the iPhone.
Odds of Apple doing this: nearly zero. The pressure isn’t going to be on Apple to license proprietary technology from RIM or Microsoft. The pressure is going to be on IT departments to support open standards like IMAP, which the iPhone supports.
At least he said, “nearly.”
I try to be a minimalist, so I tend to keep my bag pretty lean — only taking with me what I need on a regular basis.
Continue reading “What’s In My Bag?”
Spasm is a super-primitive asynchronous state machine for Node.js. While working on another yet-to-be-announced open-source project, I was looking for a way to manage logic for a CLI. For whatever reason, I thought using a state machine might be an interesting approach. I created the module in a single Seattle-to-Kent train commute and spent the following commute packing it up as a proper npm module. It’s a whopping 37 lines of code (plus 214 for tests).
Continue reading “Introducing: Spasm”
According to Pingdom, my website had an abysmal 99.67% uptime over the past year. It was down 68 times for a total of 1 day, 5 hours, and 20 minutes. Why?
Continue reading “So Long, Tumblr”
Hungry for more? Hit the archives.