Hi, I watched quite intersting Rails video last week (http://goruco2009.confreaks.com/30-may-2009-14-45-into-the-heart-of-darkness...), here are the most interesting suggestions I remember: 1) Know APIs - it is very important to know the standard Ruby library and Rails enhancements to avoid reinventing wheel in your code and write the code efficiently. See http://ruby-doc.org/core http://ruby-doc.org/stdlib http://api.rubyonrails.org 2) Learn common Ruby constructs like value ||= 1234 (instead of: value = 1234 if value.nil?) if value ... (instead of: if not value.nil?) 3) Define a common coding style and document it, ensure that new team members read it and are familiar with it. Document every decision you make. 4) Use tools like 'reek' to check the quality of the code 5) Write useful tests (do not test components outside your application) 6) Use a build server (like Integrity or Hudson) The video contains more tips, it's worth of seeing. -- Best Regards Ladislav Slezák Yast Developer ------------------------------------------------------------------------ SUSE LINUX, s.r.o. e-mail: lslezak@suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Prague 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ -- To unsubscribe, e-mail: opensuse-ruby+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-ruby+help@opensuse.org