I think generally, rails is built for productivity, people sometimes confuse this with it being easy to learn. It isn't, it's very large and solve many different problems. It takes a lot of time to learn the framework, but once you do, you can leverage a lot of the complexity to build things very, very quickly. Colin's suggestion is very good, find a gem that you use, learn it, read the source fully, then see how it can improve or address issues as they come in.
In response to the OP, in general, the low hanging fruit has already been taken. A lot of the bug fixes now are pretty extreme edge cases that require a fair bit of understanding to every describe why it is a bug. Colin's suggestion is very good. Find a gem you use, learn it, read the entire source code, then address issues as they come in. http://www.codetriage.com/ might help as well. Best, On Thursday, September 17, 2015 at 3:22:03 AM UTC+10, Hunter Stevens wrote: > > Sorry, I meant it is easy in theory. In practice it is still difficult > with, like you said, so many little nuances. > > On Wednesday, September 16, 2015 at 1:12:28 PM UTC-4, Elizabeth McGurty > wrote: >> >> Hunter: Seriously you are joking... >> >> >> On Wednesday, September 16, 2015 at 12:52:09 PM UTC-4, Hunter Stevens >> wrote: >>> >>> The reason why Rails is so easy to work with (in practice), is because >>> the framework's source code is so complicated and intense. Or else the >>> end-programmer would be required to a lot more themselves. >>> >>> On Wednesday, September 16, 2015 at 12:46:23 PM UTC-4, Elizabeth McGurty >>> wrote: >>>> >>>> AMEN! >>>> >>>> Colin writes: "Rails core code is not the easiest code to get to grips >>>> with." >>>> >>>> What an understatement! I am actually an advanced mathematician with >>>> that training in precedence and exception and for years I have worked with >>>> ROR -- in its history of versions. I'll write with considerable >>>> confidence >>>> that it is extremely difficult to learn the nuance of ROR. (Watch >>>> Railscasts, and you want to abandon your profession. How/where does Ryan >>>> Bates learn this nuance?) I see 'authoritative" code examples here and I >>>> have no idea from whence they originated. As a starting point the >>>> documentation needs to be improved. Just as an obvious example, such >>>> frequent questions here are related to table/model associations. >>>> >>>> Liz >>>> >>>> On Wednesday, September 16, 2015 at 10:30:50 AM UTC-4, Colin Law wrote: >>>>> >>>>> On 16 September 2015 at 14:15, Chirag Aggarwal <chi...@gmail.com> >>>>> wrote: >>>>> > Hi, I want to contribute in Ruby on Rails. Could someone point me to >>>>> a >>>>> > beginner bug? >>>>> >>>>> Do you mean you want to contribute to the development of Rails itself? >>>>> If so then I suggest you first register with the rubyonrails-core >>>>> list [1] and hang around there for a while to get a feel for things. >>>>> Also (and perhaps easier) you could have a look at the open issues on >>>>> any of the gems that you regularly use (devise perhaps, whatever gems >>>>> you use) and try and fix them. Rails core code is not the easiest >>>>> code to get to grips with. >>>>> >>>>> Colin >>>>> >>>>> [1] http://groups.google.com/group/rubyonrails-core. >>>>> >>>> -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-talk@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/be0cc496-3ac0-4c7f-ac74-d05b959ae9be%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
