Switching to Ruby

Whenever I was watching more TV than working on my Great Idea, it was because I was stuck. I didn’t realize it at the time, but my mind was avoiding making a tough decision or working through a particularly hard problem. My Internal FUD pushed me towards easier tasks. Watching TV was a whole lot easier than spending a couple hours researching, thinking about, and making the tough call. –7 lies that prevent your great idea from becoming a real business

Whenever I find myself not working on my project I come back to this quote, because it’s always true. Anytime I’m not working on scotchel.com for any significant amount of time it’s because I’ve hit a roadblock. My current issue can be stated simply: do I continue building the site in PHP or do I switch over to Ruby on Rails?

The answer has been hard to come by, perhaps because I haven’t really sat down to think about it. But I was tired of being “stuck” so I spent an hour this morning reviewing why I might want to (or not want to) switch to Ruby. And, as of now, I’m going to make the switch to Ruby. I’ll try to get to the same place I left off in PHP (at the very least) and we’ll see how it goes. From what I’ve read, it should be both easier and more fun, so I’m looking forward to it.