What’s the opposite of derailing?

Is it enrailing? I’m not sure we’ve got a word for it in English. But whatever it is, I’m doing it. Yesterday I wrestled with databases and web servers on my laptop for an hour or so and finally got everything lined up so that I could start experimenting with Ruby on Rails.

Simply put, Rails is a web application development framework that speeds up development like you would not believe. At least, that’s the promise. There’s going to be a bit of a learning curve at first because of the Ruby part – Rails is implemented using a language that I have never programmed in.

More details as events warrant . . .

No Responses to “What’s the opposite of derailing?”

  1. David Says:

    Every time I want to add a new object to the-system-which-must-not-be-named, I have to:

    *create an SQL file to create the table
    *create a layer 1 object to access the table
    *create a layer 2 object to apply system rules and connect the object to other objects in the system

    and possibly
    *create a form for CRUD operations on the object

    For something like a login system, this would take me several hours. Yes, this is why Rails appeals to me.

  2. spoonix Says:

    I’ve been messing around with Rails, and there’s definitely a learning curve. I didn’t really know ruby to start with, so I had that battle to fight along with adjusting to the Rails system itself. The big problem is having to look up methods (and I mean that both in terms of “functions in classes” and simply “how you do some stuff”) to get simple stuff done.

    But it’s helped nuke the tedious and boring stuff. Like creating a login system in 2 minutes or just whipping up a table and having your datastructure defined.