Wednesday, October 28, 2009

Ruby On Rails

I've read this story in "Ruby On Rails for dummies" ebook. It's interesting! I was impressed. He he!
Once upon a time, there were three little programmers. The programmers wrote code for the World Wide Web — code to give users access to a company’s database.

The first programmer was in a hurry to write her code. She wrote simple code as quickly as she could. The second programmer wasn’t quite in such a hurry. She used the traditional Waterfall methodology — a multistep process involving analysis, design, coding, testing, and deployment. The third programmer was careful and industrious. She used a heavyweight persistence framework such as Enterprise JavaBeans. She built her software to cover every possible contingency and to accommodate any future need.

As you might expect, this story has a big bad wolf. The wolf might have been a manager, a client paying for the software’s creation, or a customer attempting to access the company’s Web site. The wolf went in reverse order, visiting the careful and industrious programmer’s Web site first.

Unfortunately, the wolf couldn’t log onto the industrious programmer’s site. Instead, he got the message: “This site is under construction.” The careful, industrious programmer had completed only half of her work. The heavyweight persistence framework was difficult to learn and burdensome to use.
Needless, to say, the wolf huffed and he puffed, and he blew the Web site down.

code in place, the second programmer couldn’t easily make major changes. All she could do was fix bugs and make the code run a bit faster. She promised that she’d update the requirements for version 2.0 of the system. But the wolf was impatient. He huffed and he puffed, and he blew the Web site down.

In desperation, the wolf visited the first programmer’s Web site. She had built the site quickly and easily, using Ruby on Rails. In fact, her first prototype had been up and running in two days. Her co-workers had tested the prototype, critiqued the prototype’s features, and told her what they expected in the next prototype.

The next prototype was ready sooner than anyone expected. Once again, co-workers tested the prototype, suggested improvements, and helped the programmer to refine her evolving requirements.

After several brief rounds of coding and testing, the Web site was ready for public use. The wolf enjoyed visiting the site because the site’s look and feel reflected the way it had been designed. The site was nimble, intelligent, and easy to use. The site did the kinds of things the wolf wanted it to do because the programmer had gotten feedback on each prototype. Everyone was happy . . . for a while anyway.

To repay the Ruby on Rails programmer, the wolf offered to repair her house’s leaking roof. Unfortunately, the wolf had a nasty accident. While he was working on the roof, he fell into the chimney and landed directly into a pot of boiling water. Goodbye, wolf!

But the Ruby on Rails programmer was happy. She had created a great Web site. And with all the time she’d saved using Ruby on Rails, she was able to climb up to the roof and repair the leak herself.
The end.