On 10 January 2011 09:21, rtacconi <[email protected]> wrote: > In Ruby and Rails the most important thing is experience and having > code on Github. > But, the most important thing is to > have some good code on github, so help in a project and create your
I certainly agree that getting lots of experience with a language is good (although a fairly obvious tip). But I fail to see how "the most important thing" is to have code on Github? I don't have anything on there other than a few Gists that I've put up when helping people from this list. I use Mercurial as my SCM, so Github isn't much use to me, and the majority of the code I work on is not open source - my clients would shoot me (worryingly literally for one of them...) if I was to push their code to a 3rd party host. If you mean that it's a good thing to help publicly in a community; then again, that's true, but such a broad and flat statement as "most important" doesn't really help a discussion - especially when it's not necessarily even nearly true (as my case shows). BTW how would you suggest someone gets "good code" on github as opposed to "bad code"?... there's nothing in Github as a tool that helps you learn to use Ruby or Rails, or to write "good" code (in quotes, because the definition of "good" can vary depending on context). I'd refer the OP to the previous posts on not taking certification as point of fact of ability, and instead work through the tutorials and the books, and learn the subject of OO programming in some breadth - even if that includes learning some Java, PHP, C#, etc too - all of which will improve your Ruby by having a larger understanding of patterns used in development. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
