Tuesday February 26, 2008 02:00 |
0 Comments
I’m on the cusp of releasing version 4 of my custom blogging engine. Version 2, 2.1, and 2.5 were all based on C#/ASP.NET code and then I did something which slowed me down significantly; I ported everything to Ruby on Rails for version 3. Honestly, the learning curve was steeper than I anticipated.
It’s not that Ruby and Rails are more complicated than C# and ASP.NET, it’s the fact that during that time, I did a complete platform change as well. All of my computers back then (including email servers, web servers and workstation) were all Microsoft-based.
I was using Windows XP with Visual Studio to write my applications, using Exchange Server for my email, and using Windows 2000 with IIS to host my web applications. You get the idea.
Then it all changed. Not sure what it was exactly, I think it was a number of factors, but I decided that I was going to develop Ruby on Rails applications and if I was going to do it, then gosh darn it, I was going to do it right! When I say right, I really mean developing on a Mac and using Linux based servers.
I basically threw away years of foundation and knowledge and started from scratch. It was tough but rewarding. In time, I hobbled together version 3 of eddorre.com with the earliest of the earliest Ruby and Rails code that I knew.
Even as I was writing version 3, I knew that I would eventually re-write it again and probably even from scratch. That’s exactly what happened. A number of reasons can be attributed to this. Version 3 is based off of Rails 1.1.6 which is horribly outdated. So much in the Rails world has changed including the milestone release of Rails 2.0 (and the paradigm of RESTful development).
In addition, my knowledge of Ruby, Rails, CSS, and Javascript have grown tremendously since I released the last version.
So I threw my old code (version 3) and started anew (again). Luckily, this time, I wasn’t changing platforms. There are more features that I want to import into the project, but for now, it’s almost done and close to release (probably sometime this week). And it’s a good thing too, now that I’m fairly comfortable with Ruby on Rails, there are some other projects that I’ve been wanting to work on. So, hopefully, I can shed the self-imposed mantle of “one trick pony.”
And now for the obligatory teaser image:
