Various Links

Here is a list of various links of technologies that might be useful for development.

Git

Git for source control

Ruby on Rails

Ruby
- http://www.ruby-lang.org/en/documentation/
- Ruby syntax cheatsheet
- Ruby builtins cheatsheet
- RubyInside http://rubyinside.com/
- RubyFlow http://www.rubyflow.com/
Ruby on Rails in general (for webservice and client)
- Getting started with Rails
- Ruby and RoR conventions
- Ruby On Rails Guides, edge version http://guides.rails.info/
- Ruby Best Practices (really recommended)
Ruby on rails specifics

Screencasts and Videos

Title	Length (MM:SS)	Summary	Rating (max. 5 stars)
Scotland On Rails 2009 Ruby object model	63:27	Presentation describes ruby object model and explain all possible tips and tricks how to use it. Describes also syntax used for this tricks. Show differences between java object model and ruby one. Good introduction to meta-programing and how works objects in ruby.
Title	Length (MM:SS)	Summary	Rating (max. 5 stars)
MountainWest RubyConf 2009 Improving the Usability of Your RoR Applications	30:31	The first half is the most interesting, there are several tips how to make UI good looking and how to ensure that user feels safe and comfortable using your application. One of the examples is gmail's status message after deleting an email - it displays "undo" link in the successful message so the user can easily revert the action after a mistake. The second part displays changes in a specific application, this part was not much interesting for me. Good even for non-UI designers, at least the first part.
MountainWest RubyConf 2009 Building Blocks of Modularity	32:55	This video describes kinds of bindings between parts of an application and how to make the bindings weak so changes in one module affect the other modules as least as possible. Nice video, worth of seeing. Usually known facts, but grouped together in an interesting context.
Gotham Ruby Conference 2009 Into the Heart of Darkness: Rails Anti-Patterns	40:01	Anti-patterns are wrong solutions which people do again and again when solving a common problem. This video describes how to avoid anti-patterns in Rails - study standard libraries in Ruby and Rails, do code review in team, discuss/set common rules and document them, use metrics to check the code (reek or metric_fu), use a build server, don't write useless tests... A must-see video, describes how to avoid common problems in Rails.
Gotham Ruby Conference 2009 SOLID object oriented design	47:11	Good presentation which describes why DRY, test-driven and other techniques is not enough to have good code. Describes with examples how to good design code to don't scare that your product succeed and have to maintain it hard. Must see if you want improve your coding style, your code and if you want understand why rails is so popular and why it have such interface as it has. (five stars is not enough :)
Rails casts Rails 2.3 extras	9:50	Presents what is new in rails 2.3 (so it not include last features for 2.3.4). It contains explanation how works batches (work db by parts), scope ( set scope of model or query) and try method (safety call of method, really useful method). Really good video if you don't know described functionality. But it doesn't go deep, so if you know that features then it is waste of time for you.
Rails casts Seven security tips	14:42	Shows seven most common security problems in rails application with demonstration how to attack and how to defend. It contains mass-assigment, uploading file, logging passwords, CSRF protection, authorization ownership, SQL and HTML injection. Good video to prevent common mistakes. You can create simple checklist to avoid this common failures.
Scotland On Rails 2009 Ruby code review dialog	42:50	Imaginary dialog with project leader and code ruby expert which shows common mistakes in development. It is focused on two main issues. The first one is breaking of old test during developing new features (breaking fixtures) and automatic deployment server (Hudson). The second one is bad usage of meta-programming and some rules which should be followed to not break working stuff with injection to shared objects. Really good funny presentation. To reach five stars it missing more details and also way to avoid fixtures is little controversy.