So – work has pushed me to using Rails. We’ve been wanting to do Rails work for a while, and I helped land a project that is a good fit: it’s big enough and should fit into an MVC paradigm nicely – plus it doesn’t need e-commerce or complicated shipping logic like many other End Point projects seem to.

I was initially hesitant to learn a new framework. . . I don’t know if this was intentional or not, but it was put out to me thusly – “if you don’t do this project in rails, we’ll get someone else to, even if it means hiring an outside consultant.” The surest way to get me to do something is to tell me I can’t. :)

I’m relatively new to rails, but not new to web development generally.

Other web development frameworks¹ I’ve gotten (more or less) good at over the years:

• Mason
• CGI::Application
• Interchange
• WebGUI

And others I have a more-than-passing knowledge of:

• Zope
• Catalyst
• Various PHP apps – phpBB, Moodle, etc.

I was also a longtime MySQL fanatic until I came to End Point and discovered that a database can be more than a glorified storage engine: It can also save you oodles of development time and protect your data. All hail Postgres!

Here’s where I plan to keep track of my Rails process and what quirky things I discover along the way.

¹ Where “web development framework” has a VERY loose definition.