# List of features to be concluded for create a Rails Demo?

**URL:** <https://www.ruby-forum.com/t/list-of-features-to-be-concluded-for-create-a-rails-demo/150774>\
**Category:** Rails\
**Created:** [October 13, 2008, 6:49am UTC](https://www.ruby-forum.com/t/list-of-features-to-be-concluded-for-create-a-rails-demo/150774 "2008-10-13T06:49:30Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![mokkai](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/c2a13f/32.png) [@mokkai](https://www.ruby-forum.com/u/mokkai)\
**Post date:** [October 13, 2008, 6:49am UTC](https://www.ruby-forum.com/t/list-of-features-to-be-concluded-for-create-a-rails-demo/150774/1 "2008-10-13T06:49:30Z")

</div>

hey all,

i need to create a good & attractive Rails-2.1.1 Demo presentation(with  
the full working flow)  
what are the main features should be concluded in presentation ?

---

<div class="post-metadata">

**Author:** ![mokkai](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/c2a13f/32.png) [@mokkai](https://www.ruby-forum.com/u/mokkai)\
**Post date:** [October 13, 2008, 5:56pm UTC](https://www.ruby-forum.com/t/list-of-features-to-be-concluded-for-create-a-rails-demo/150774/2 "2008-10-13T17:56:55Z")

</div>

That depends entirely on who the audience is…

If you’re trying to convince someone to adopt RoR for development, the  
most powerful arguments I’ve done are to show an existing app with some  
substance, then show how RoR makes life easier for the devs, faster  
turn-around for the clients, functionality versus lines of code (that  
convention over configuration argument). Show 'em a development  
environment, tweak the app in front of them. That’s probably what  
they’ll appreciate, and where they’ll see value.

If you’re trying to convince potential clients, scaffold something in  
their domain (and pretty it up) to get their attention. Make it relevant  
to them, regardless of what your last whiz-bang project was. My own  
experience is that people in general like concrete examples that they  
understand, you want the technology to be new, not the domain: “I make  
custom furniture, why are you showing me an auto parts catalog?” (you  
just have to make sure you understand at least some portion of their  
domain space as well so as not to look the fool).

---

<div class="post-metadata">

**Author:** ![mokkai](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/c2a13f/32.png) [@mokkai](https://www.ruby-forum.com/u/mokkai)\
**Post date:** [October 14, 2008, 8:28am UTC](https://www.ruby-forum.com/t/list-of-features-to-be-concluded-for-create-a-rails-demo/150774/3 "2008-10-14T08:28:33Z")

</div>

Ar Chron wrote:

> That depends entirely on who the audience is…
> 
> If you’re trying to convince someone to adopt RoR for development, the  
> most powerful arguments I’ve done are to show an existing app with some  
> substance, then show how RoR makes life easier for the devs, faster  
> turn-around for the clients, functionality versus lines of code (that  
> convention over configuration argument). Show 'em a development  
> environment, tweak the app in front of them. That’s probably what  
> they’ll appreciate, and where they’ll see value.
> 
> If you’re trying to convince potential clients, scaffold something in  
> their domain (and pretty it up) to get their attention. Make it relevant  
> to them, regardless of what your last whiz-bang project was. My own  
> experience is that people in general like concrete examples that they  
> understand, you want the technology to be new, not the domain: “I make  
> custom furniture, why are you showing me an auto parts catalog?” (you  
> just have to make sure you understand at least some portion of their  
> domain space as well so as not to look the fool).

Thanks for you reply  
They are also developers & new to ROR  
but they are strong java developers for past five years  
at which features i should take good concentration ?

---

<div class="post-metadata">

**Author:** ![mokkai](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/c2a13f/32.png) [@mokkai](https://www.ruby-forum.com/u/mokkai)\
**Post date:** [October 14, 2008, 6:33pm UTC](https://www.ruby-forum.com/t/list-of-features-to-be-concluded-for-create-a-rails-demo/150774/4 "2008-10-14T18:33:38Z")

</div>

Pokkai D. wrote:

> Thanks for you reply  
> They are also developers & new to ROR  
> but they are strong java developers for past five years  
> at which features i should take good concentration ?

Umm… what is it that YOU like the most about RoR? Those would be the  
easiest points for you to speak about, and work up an example to  
showcase.

I like Ruby, I like the MVC and how it is ingrained into Rails. I’m a  
huge fan of haml for the views. The combination of these things just  
sings (for me at least). I like being able to easily leverage other  
people’s Gems into my application. The Rails community is another big  
plus in my book, and to say nothing of “Fred” would be a horrible  
omission. 😉
