my Technology Blog Follow @rhatol

I've been trying out Ruby on Rails for a week now (during my free time). I'd say it's a very good MVC Web Framework. I started with scaffolding then all the ways down to its in internals. Routes file, ORM, Rake, Migrations, TDD, helpers, validators, associations...all the way through Rack. I'm glad to find out that many modern programming/architecture concepts are now mainstream, meshed together on these frameworks.

I haven't done much pure large-scale coding work since I started handling software R&D but my intentions on learning Rails is for Prototyping/RAD.

As a background, we find quick, cost-effective, reliable, alternative solutions for software requirements in our company. In which more often translate into utilizing Opensource software (Well, of course).

You can't always find the right Opensource software (or at least a near fit) to your customer's problems, and there will come a time where the best way in finding a solution is to just quickly create a prototype where everyone can immediately understand and appreciate the problem/solution.

So when that worst case scenario arrives, we can just do it in Rails with scaffolding here and there (don't laugh, I learned quickly through scaffolding and I know, you can only use scaffolding up to a certain point and ideally only as a guide if you're just starting out) then, Boom! "Can everyone now realize the simple problem or solution to this issue? Thank you." It's just kinda like an "Ace up your sleeve" thing...

There's already a lot of resources on the net so I will not waste your time providing links here and most likely just end up to the usual Rails resources out there.

KUNG HEI FAT CHOI EVERYONE!!!!!!!

Labels: chnese new year, Rails 3, research, Ruby on Rails, web framework