Rails Mania

Jun 23, 2006 10:22

Everyone has been frothing at the mouth about Ruby on Rails this week. The primary cause was most likely the two days Rails class that someone was putting on. We often put on classes here that are taught by people internal to our company. Anyone can attend, provided they can convince their boss to pay for it and give them the time to do it. Rather ( Read more... )

Leave a comment

Comments 4

flubz June 24 2006, 03:03:22 UTC
I don't understand everything in this entry, but I watched a few
quicktime demos of ruby on rails and it looks pretty neat. Granted
they were abreviated explanations and assume pre-knowledge of a number
of things (AJAX etc) but otherwise I like it.

Reply


Interesting walterwz June 25 2006, 13:29:33 UTC
I will have to this out. Python currently occupies my "interesting but not immediately useful things to learn slot." Rails seems to tout all of the same things that .Net promises.

Your point about the legacy systems is awesome. Those things just tended to accumulate like a coral reef. There is about as much rhyme or reason. My biggest problem with legacy stuff is that it is an unstructured mess.

Current theories on refactoring make sense here, though refactoring is a buzzword used to dazzle mindless management. The interesting thing I am finding there is that when you do approach a project with good OO design very large amounts of code becomes redundant and goes away.

Reply

Re: Interesting urbanomad June 25 2006, 13:49:32 UTC
Don't be deceived. OO is as much of a buzzword as all the others. There are many tiers of buzzwords, all the way from SOAs and ESBs to .Net and Rails to OO and MVC. None of them is necessarily THE answer, they're all just tools to help you get organized, but no matter what you use you can still screw it up. Rather than focusing on what tool you use and saying "Oh it's using Rails so it'll be better", it's more important to say, is it readable and maintainable? To people other than ME? Usually, for this to be true, it leads to, is it well documented? Is it portable and written in a way that other people can reuse the code on other projects? If I wanted to completely port the code to some other tool, is that easy or is it hard? These are the questions that I think are more important to ask.

Reply


ria777 July 12 2006, 15:12:06 UTC
Ria here from last night. please e-mail me, so that I can send you my contact information. thanx.

Reply


Leave a comment

Up