> > If a developer cannot figure out how to do X from the docs, she should > complain about it > instead of assuming it's perfectly normal to spend time reading the source > to figure out > how to use something.
I generally agree with this, but not all code authors are willing to listen to you, either because they are bored or because their ego doesn't let them (to accept that they had a flaw in docs/code)....so, most of the time I just look at the source, even if i do make a post about the lack of documentation. It's faster in most cases :) @Jim, no worries, I understood that you didn't mean "read the code before you post next time" :) On Wednesday, March 27, 2013 12:37:28 PM UTC+2, Michael Klishin wrote: > > > 2013/3/27 Ryan <areka...@gmail.com <javascript:>> > >> I believe Jim meant to check the source to figure out how does it work, >> not that the way it's implemented is the most proper way to implement it. >> If that's not what you wanted to point out can you please explain? >> > > If a developer cannot figure out how to do X from the docs, she should > complain about it > instead of assuming it's perfectly normal to spend time reading the source > to figure out > how to use something. > -- > MK > > http://github.com/michaelklishin > http://twitter.com/michaelklishin > -- -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
