Vinsol (Basically Vinayak Solutions Pvt. Ltd.) is a small software firm in Delhi (India), growing rapidly with fast pace due to its employees’ hard work and dedication. I had worked with Vinsol for 4 years. It being my first company, I give it all the credit for giving me so much of knowledge in every aspect of wed development cycle. They deal in Ruby on Rails, IPhone, Android and are developing some remarkable applications. It has great environment and tremendous work culture. They all are fresh and young brains coming together to take Indian Web Development Industry to great heights. To know more about it visit http://vinsol.com.
March 29th, 2007 at 9:20 am
Hi Vinsol community,
Good to see people like you, highly dedicated to RoR.
I am working with ROR for around since last 6-7 months, trying to explore more and more on it. Not doubt its facinating and supporting while development.
I would like to share your experiences with the technology.
Your experiences can be ur own….. or anyone else experiences thats worthwhile…….
You put forward ur step…… and I wanna wish to take your efforts to a complete help book for ROR people.
I put forward a topic regarding best practice coding in ROR at the basic level to start with. Lets share our thoughts.
Few common conventions suggested evry next time while creating a best practice code are:
1. Stick to the Conventions.
2. Don’t Repeat Yourself.
3. Refactoring.
4. Validations must be the part of model.
5. Keep the Logic in Models.
6. The database script should be available with migrations.
7. Inheritance and Relationships between tables must be defined in Models.
8.Test-Driven Development, that involves repeatedly first writing a test case and then implementing only the code necessary to pass the test.
9. Performance testing should be done in the production environment, as this adds some optimizations which are usually turned off in the development environment. Its a last thing to be suggested….. when u r abt to make a launch of ur application.
Explainations:
“Stick to the Conventions”
It means how we name our…..models, controllers, views, test, ……………….., database, table, fields………….
“keep the logic in model”
It seems many beginners have difficulty determining what code to place in models. As a result, the models are very small but the views and controllers are littered with business logic. More often than not, if you can move something out of the view/controller and into a model, you should! This has many benefits, including slimming down the views/controllers, removing duplication, and making it easier to test this logic.
“Refactoring” is used to improve the design of existing code without changing its functionality. Keeping the logic in models can also be helpful in refactoring.
Looking forward to som1 complete the list of common conventions……….
April 3rd, 2007 at 10:02 am
Validations Must Be Part Of Model
http://debasishg.blogspot.com/2006/08/validation-logic-wire-up-using-spring.html
try the above given link
Validators are tier agnostic and can be used to collaborate with multiple layers -
* Business Layer for enforcing business logic on “semantically valid” objects
* Persistence layer to ensure valid objects get persisted
* MVC layer to enforce data binding from request parameters
Validators in Spring have their lifecycles controlled through the IoC – hence these singletons can be nicely wired together through DI
Spring MVC requires validators as separate objects
April 4th, 2007 at 10:42 am
k lets not make the ‘Vinsol’ section flooded with Rails concept…… lets better move to ‘Rails’ section to continue discussing the concepts
.
Its somthing for ‘Vinsol’ people I guess.
August 28th, 2008 at 7:13 am
good tutorial
i appreciate ur approach