Michael, what do you say is very correct and I do that!
But, my working process is different, I take you an example. Now Im very very interesting in couchdb, so Im also interesting in merb and datamapper, and for datamapper there is an adapter for couchdb. Right? I want simply understand two things: 1) associations works with couch db? All? All like mysql? 2) validations? So, my first things is, search somewhere is this dm-adpater do that. If yes, then I inspect the code for see all undocumented fatures and yes learn some new things. This because, every day I see some interesting things, so for all I can't learn all the source because I will spent a lot of time. On 16 Nov, 19:54, "Michael Klishin" <[EMAIL PROTECTED]> wrote: > 2008/11/16 DAddYE <[EMAIL PROTECTED]>: > > > Or if they never build a blog or a website / smallcms is possible to > > make a good app, so people in this way have a good starting point for > > learn. > > I agree with all said here but don't expect 10 more Merb blogs at > github tomorrow. > Simply because to put something online you have to make it more or less sane. > This is how open source can be used: to judge skills (or level of > laziness) of other people. > > > For example, the default orm, datamapper can be good, but how use It? > > Is (my opinion) poor documented, and for my society, I've a lot of > > trouble using It, simply because, I don't know It and I don't know If > > any big society use it. > > You probably mean community, not society. I am going off topic here a > bit but this question is > something I never skip. The answer is, *read the code*. > The only way to not depend on documentation writers, developers, > version mismatches > and so forth is to read the code of what you use. > > Not only it would make you 100 times more efficient with your tools, > it is the only way to not depend on others. > Core teams and contributors come and go, your applications should not > depend too much on it. > > So given Merb and DM is mostly easy to understand and it's in Ruby, a > very readable language, > read the code from time to time, and you'll never care about number of > tutorials, > open sourced applications, typos and mistakes in the wiki, > damn-slapp-tutorial-being-constantly-out-of-date, you name your > documentation issue. > > Source is there, it never lies, it's extremely high level language and > it's written with idea of > NOT using meta programming for meta programming's sake (some call it > "beautiful code') > and smartpants tricks as much as possible. > > I don't remember who and when made me think about topic but I > definitely feel thankful to that person. > I learned 1000 times more from the source of projects like Merb, > DataMapper, MooTools, Mercurial, Twisted and Git > than from all Ruby, Python, C and JavaScript books & documentation > chapters I have read (a bunch). > > So read the source. or you'll be bitching about "that core team that > never writes docs" for the rest of your life, no matter what you use. > -- > MK --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" 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/merb?hl=en -~----------~----~----~----~------~----~------~--~---
