Linked by David Adams on Fri 11th Jul 2008 02:59 UTC, submitted by snydeq
Thread beginning with comment 322532
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Be conservative
by modmans2ndcoming on Fri 11th Jul 2008 21:51
in reply to "RE: Be conservative"
RE[2]: Be conservative
by StephenBeDoper on Fri 11th Jul 2008 23:16
in reply to "RE: Be conservative"
The main reason is this: Ruby on Rails developers know an important design pattern; MVC.
That's certainly useful, but it doesn't guarantee that a developer can apply those principles beyond the specific framework they're familiar with.
Or put another way, the important question (IMO) is: can a developer adhere to good practices even if he's not working within a framework those which enforces those practices?
Personally, if I'm hesitant to work with anyone who is only capable of doing their job using a specific set of tools - proficiency is good, utter dependency is not.






Member since:
2005-07-05
One other comment...
While I agree with you that a Sharepoint programmer is probably worth a bag of cotton candy (maybe even a big bag), or a half-melted ice cream cone melting down a child's hand (maybe even a double-scooper), if that's all they know, I don't agree that Ruby on Rails programmers fit in this group for a variety of reasons.
The main reason is this: Ruby on Rails developers know an important design pattern; MVC. Ruby on Rails is fairly slow, but it encourages some excellent programming practices, whereas web languages like Java and the .NET framework don't. In fact, I think VisualStudio encourages some fairly poor development practices, to be honest.