andyman’s posterous

Can you spot:
1. Leather couch?
2. Big Foam block?
3. Waldo?
 
One time there was even an entire queen-sized bed floating in there.

I started learning Ruby on Rails programming language and framework about 6 months ago and have been using it quite extensively to develop my first Rails web application, Headmagnet. (I am a former Java and PHP developer)

Here are my miscellaneous thoughts and lessons learned on Ruby on Rails:

1. There is a learning curve to learn the Ruby programming language, and also one to learn the Rails framework. Everyday, I find features of Ruby, and features of Rails that I didn't know that I didn't know - which makes it harder to proactively learn.
2. Even with the learning curve, I could code stuff up a lot faster with Ruby on Rails than with Java (and I'm supposedly fast at Java), and much cleaner than with PHP. I wouldn't want to go back to Java or PHP, except when work really requires it.
3. There's quite a difference between doing Ruby on Rails the way you write Java or PHP, and doing Ruby on Rails the "right" way. The "right" way usually tends to be a lot less lines.
4. Too many old Rails tutorials are old and obsolete. There were big changes in Rails 2. Look for Rails 2.x.x tutorials. Although many of those tutorials were written for an audience for already knew Rails.
5. Having good and quick Ruby documentation and Rails API documentation in your bookmarks is indispensible. I'd recommend Railsbrain for downloading the Rails API docs for fast local access.
6. The production environment in Rails for Mongrel is MUCH MUCH faster than the development environment. (more than 10x faster). I didn't know this until too late in the game, after much optimization work had been done.
7. Named scopes are great, allowing you to combine multiple conditions and parameters for queries. I wish I knew about this one earlier.
8. There are tons of plugins and gems. The three I'm most thankful for are: will_paginate, restful_authentication, and jrails
9. As a proponent of separation of content, behavior, and presentation, I hate the javascript that Rails generates and embeds into the html. I love the convenience it offers though, that view methods like link_to_remote, or remote_form_for offer though.
10. Writing and testing custom Javascript to do stuff more "properly" can take a lot longer than just using Rails view helpers to generate the view. 
11. It's much easier to test models than controllers. You can also play with models easily thorough the rails console, and explore what you can do with them. I guess this is why they say to keep the controllers small, besides for reusability. I find the same with helpers.
12. Autotest sure helps with continuous testing. The Rails console is useful for digging deeper and playing around with models. It can be a bit distracting though, breaking the focus/flow when coding.
13. Slicehost is a great VPS for hosting Rails. Even if you don't use them, but want to set up an Ubuntu Linux server from scratch with a mail server, mysql, nginx server (a fast lightweight server), Ruby on Rails, and Mongrel Cluster (a bunch of Mongrel servers), they got awesome documents. If you do sign up with Slicehost, please use this referral.
14. There's an overhead for calling view partials, especially if you call it in a loop. Just don't go crazy breaking things down into a million little view partials if you don't need to. Its hard to work in editors with when there are too many files to flip/browse between to find the right place. Originally when developing Headmagnet, I broke views down into many view partials to make the site more AJAX friendly and convenient to use with RJS. But soon, I had dozens of little partials and it got hard to manage and read. Later on, I simplified and consolidated drastically, as well as just wrote custom javascript to take care of things more efficiently and more responsively.
15. The Rails migration features are quite useful, especially the incremental migrations where you are just adding a column to an existing table. Don't worry if you have a lot of those during initial development. You can consolidate them later if you want to. Just refer to the db/schema.rb as your reference for what columns are where.  Don't do like I did at first in using the migration files as my reference, and change old migration files to add new columns and indices and then drop, recreate, and remigrate. Just remember also that when you add new columns via migrations, it doesn't automatically update any tests. 

I hate the new game Fallout 3. I hate it because I love it too much. It is too addicting. Way too addicting. I've spent countless hours playing it since this past Saturday after launching the public beta of Headmagnet, my new web app that lets you memorize stuff quickly, and predicts when you forget things. (Well, I needed a good break after months of grueling workdays slaving away at code and dealing with web browser inconsistencies. Besides, I'm waiting to collect some user usage data from the beta test.)

Fallout 3 is a game set in post-apocalyptic Washington D.C. area after a nuclear war. You've lived in an underground vault all your life and am coming out to the surface for the first time.

Some really innovative features I've found about Fallout 3 so far, without giving any real spoilers:

1. Character Creation: The character creation process is so original and unique, almost like real life. Your new character starts literally from the moment of birth as a newborn. The tutorial steps follow through at the ages of 1 where you learn how to walk, 10 and 16 where you set up your character's skills and abilities. By the time the real game starts, you're fully immersed as the character.
2. Immersion and Artwork: The post-apocalyptic world they created is so immersive and real looking. The first steps out of the vault where the character has lived since birth, are breathtaking and staggering -- and in real time! Not a movie. Excellent artwork and design.
3. V.A.T.S. system: The V.A.T.S. system for pausing combat, and choosing targets to attack is great for those who are not fast first-person shooter gamers like myself. It was a good way to integrate the mechanics of Fallout 1, Fallout 2, and Fallout Tactics, which were all top down games where things were much more dependent on the character's stats than the player's own reflexes and mouse skills.
4. Open-endedness: just like in the Elder Scrolls series by the same company, Bethesda Softworks, you don't have to follow the main storyline, and can wander off on your own and just explore or do one of thousands of side quests. I haven't really even begun the main plot yet, but have managed to somehow spend two dozen or more hours playing the game.