ron rocks the mic

yo yo this is ron.

i hope bobo won’t be mad that i’m posting here.

the man is getting interviewed, trying to be a rok star, talking about himself. credit where credit is due, baby.

this type of thing, where all the admins are in one place, talking about the music we love and the scene that confuses us and interests us all at once is a very cool thing indeed.

even though i pay a relatively small part in the project, it’s a day like this that reminds me that this thing is less about the code and more about the crew.

where the hell are you shepandmays?

  1. Andy says:

    [quote comment="4708"]I do bevleie that a programmer should learn atleast ONE language and be an expert in it OR in the not too distant future I see (in disbelief) a client getting refused a feature just because a particular framework does not have it [/quote]Of course once you learn one language it is usually easy to pick up other ones. There are bunch of paradigms and concepts that one needs to learn once, and then can successfully applied in every language: stuff like inheritance, polymorphism, recursion and etc are present in nearly all sufficiently complex and advanced languages out there.What RoR has going for it is rapid development. For example, the company I mentioned decided to switch their app from a dinky MySQL server they started with to a powerful Oracle box because. How long did it take them to port the application to the new DB? Not counting the data migration, it took less than a minute.All they had to do was to bring down the application, change 3 lines in a config file, and start the application again. It's because the developers haven't wrote a single line of SQL or a query statement during the development. They just worked with objects and everything was handled internally by Rails. When they switched databases, all the queries were dynamically adjusted to work with the new server.I had to do something similar in PHP once but fortunately I knew ahead of time that my application would need to work with either MySQL or MS SQLServer so I wrote a class to do all the database operations and had to double-check all the queries to make sure they will work in either server. In most cases it seems that Rails developers do not have to concern themselves with this kind of stuff.This is why they were so absolutely in love with the framework. a0|a0

Post a comment

Name or OpenID (required)

(lesstile enabled - surround code blocks with ---)