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 ? -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
