ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

Ruby Mastery

Updated on September 23, 2008

Ruby Masters

The "Path to Ruby Mastery" is a Weekly Interview Series by top trainers and developers in the Ruby community, from across the globe. The interview series will provide insight and commentary from these notable Ruby Masters, with the goal of facilitating and providing answers to the questions Ruby beginners face.

First in this series is Little Known Ways to Ruby Mastery by Jamie van Dyke.

The following quote by Jamie is of utmost importance: "What interests me most about Ruby developers that I hire isn't their current skill level or expertise. I'm not interested how clever they can be with their meta-programming-fu, I'm interested in their use of the language. Yes it's nice if a candidate is able to do the most advanced Ruby, and I wouldn't disregard a potential developer for using it. However, I've seen far too many developers weaving layers of clever code together merely because they know how.

The most important part of developing for me is maintainability. How well can their code be picked up by other developers? This is high on my importance list. Keep it Simple Stupid (KISS) is one of my practises, so I expect any one I hire to do the same. That's not to say that they won't need to be able to understand complicated code or be able to fire out some, anyone who wants to pick up Rails and dabble in the source code certainly needs to be fluent in these methods.

When I hire someone I want to see their code and their attitude towards it. Open Source software is the first place I look to see what they've done. Contributing to other peoples frameworks shows an ability to understand other developers code, and more importantly, that their contributions were good enough to be accepted. If there are no contributions to other peoples software, they'll struggle against others I might have on my list."


    0 of 8192 characters used
    Post Comment

    No comments yet.