Reading 400 Feeds with Newsbeuter
Code: feeds, Linux, web
Comments Off on Reading 400 Feeds with Newsbeuter
I posted a few years ago about looking for a good Linux feed reader and a reader’s email reminded me to revisit the topic. It’s time for another blog post where I talk about how I overthink some part of my daily routine but it lets me do in a few minutes what I could otherwise waste a few hours on.
Redirecting Users’ URLs
Code: human-readable, URLs, web
Comments Off on Redirecting Users’ URLs
I got an email in response to an old post on how I designed NearbyGamer‘s discussion URLs. It asked how to create readable URLs for a community site where users might edit those URLs. What happens after users have made lots and lots of edits?
Biz: gems, ListLibrary.net, mailing lists, RailsRumble, Ruby, web
Comments Off on Small Plans
My last day at the Post is Feb 20, and I’m headed to Chicago on the 22nd. I’ll be helping a family member recover from surgery, so my schedule (both day-to-day and how long I’ll be in town) is pretty vague, but I’ll be around at least a few weeks before returning to DC.
Greasemonkey Scripts: Gamasutra and Arlington Library
Code: Arlington Library, GamaSutra, GreaseMonkey, web
Comments Off on Greasemonkey Scripts: Gamasutra and Arlington Library
I signed up to userscripts to share a few of the GreaseMonkey scripts I’ve written. If you’re not familiar, GreaseMonkey is a way of reprogramming websites for your own convenience, and userscripts is where folks can share what they’ve done.
Code: AASM, Bort, ConfReader, design, haml, open_id_authentication, Paperclip, planning, Rails, RailsRumble, resource_this, restful_authentication, RSpec, scheduling, teamwork, web
Comments Off on RailsRumble Postmortem
I failed to launch my Rails Rumble project ConfReader. Why?
Code: crunch, experiment, Rails, RailsRumble, web
Comments Off on RailsRumbling
I’m participating in RailsRumble this weekend, from 8 PM Friday to 8 PM Sunday. The goal is to build a web application in Ruby on Rails in 48 hours, and I welcome the change of pace of a small project. It’ll be a fun weekend crunch to build it, and I hope it will be a long-term resource for the development community.
WWW Will Never Die
Code: DNS, domain names, GTLDs, ICANN, web
Comments Off on WWW Will Never Die
ICANN is moving steadily to enact a fast-track process for gTLD creation (where “fast” here means “months instead of years”), so there could be a few more competitors for .com, .net, .pro, and the rest of the gang in a year or two. Some of the early candidates are .bank, .nyc, and .paris.
What this means, of course, is that www will never die. When a website could be advertised at “strand.nyc” or even just “google”, there needs to be something to indicate to the viewer they should go type this into their computer. It’s not going to be “Hey, now that you finally get that .com isn’t some kind of stutter, type this into your computer:” and it’s sure not going to be “http://”. It’s going to be www, and it’s going to just barely be the lesser of several evils for a long while.
Painless Upgrade to Rails 2.0
Code: ActiveResource, NearbyGamers, Rails, Rails 2.0, routing, Ruby, TDD, test, testing, tests, upgrade, web
Comments Off on Painless Upgrade to Rails 2.0
I spent a dead-easy 2.5 hours last night updating NearbyGamers to Rails 2.0. My svn commit message read (with links added here for convenience):
Because Internet Explorer is a Failure, That’s Why
Code: browser support, browsers, failure, Firefox, Internet Explorer, support, web
Comments Off on Because Internet Explorer is a Failure, That’s Why
About once a month since Firefox came out and was promptly recognized as a six-gallon bucket of awesome I read a blog post about how developers are lazy, shiftless bastards because they don’t want to support Internet Explorer anymore. Most recently I read Brian Reindel make this claim, so I’m going to pick on him while I rebut this insult.