Hello RoR Developers, I'm currently not a developer anymore, I'm a project manager, that adopted really eagerly agile methodologies.
One of the things that I identified while working is that, while agile already gave me a boost while managing my projects, it sometimes slacks by not using a really productive tool. You end up, having to build tons of modules, for a different variety of scenarios, to compensate for the an unproductive language. What if you constantly switch groups? What if the code you produced is proprietary? The bottom line is, how do I keep up my team productivity? Here I come searching for new horizons. Enter the Ruby world. >From a Project Manager POV, I need to know a couple things before deciding my approach on a given project. - Can x (Technology, Language, Framework) accomplish my goal? - How long would x take to accomplish it? - How easy is it to maintain? - Whats the depth of its documentation? - How easy is it to get help? - How easy is it to deploy? - How easy is it to test? Does it have integration tests (Use Case -> views -> controllers -> model -> persistence -> response) ? And how easy is it? - What x can't do? - How well does x scale? - How easy is it to persist data and work with database? How easy is it to swap database vendors? - How well does x work with caching? Basically from a couple question, I can define my schedule, my cost, my risk and quality. I also try to get my hands dirty, so I will not blindly accept someones input. I would love to hear from you guys on this question, specially on scalability, data persistence, caching, tests and deployment. Cordially, Rodrigo Dellacqua -- 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.
