Today we will talk about code organization in Ruby on Rails projects. As everybody knows, Ruby on Rails is a conventional framework, which means you should follow framework architects’ decisions (put your controllers inside app/controllers, move all your logic into models, etc.) In this write-up I will try to summarize my personal experience and show how I usually solve these problems.

Ruby on Rails, or just Rails, has allowed thousands of developers to create complex applications rapidly in a consistent manner. This level of consistency and re-use of code Rails helped pioneer has also given rise to the concept of a Web application framework, where components are used for common tasks like database connectivity.

I have recently been thinking about learning a web framework. At this point I’m looking for at rapid development type framework so I can see results without typing a whole lot of code. I’m starting to get into Python again and was looking at Django. The other options I’m considering are Ruby on Rails and ASP.net...

Rails 2.3 delivers a variety of new and improved features, including pervasive Rack integration, refreshed support for Rails Engines, nested transactions for Active Record, dynamic and default scopes, unified rendering, more efficient routing, application templates, and quiet backtraces.

A not-so-well known feature of ActiveSupport is its ability to handle blocks as definitions for custom date and time formats.