On Sep 5, 2013, at 10:25 AM, kilon <[email protected]> wrote: > A big thank you from me as well , PBE definetly made possible to use Pharo. > If I had to read pharo code to understand how to work I would be right back > with python by now.
thanks. > Pharo can learn tons of things from the success of python , I am very glad > to see that you guys put big priority on Documentation as python does. > Youtube also has loads of squeak and pharo video tutorials. So thing > actually are much better than I initially feared. > > The problems is that smaltlalkers tend to overestimate smalltalk and not > document their code. They believe too much into "self documented" nonesense > and this article hits the nail on the head concerning this problem. AFAIK > the best way to code is by writting documentation at the same time. Unless > you are the type of coder that tends to rewrite his library 10 times before > releasing, which I seriously doubt. Python has been a huge success as a > language because developer take documentation extremely seriously. Yes I would love that Pharoers have the same spirit. > I have not forget about documenting nativeboost, I will try to write a small > article on my blog about nativeboost and the things I learned which may help > you use it as part of the nativeboost documentation. If you have any request > dont forget to ping me. We want the blog :) And also your feedback on the nativeBoost chapter. > > > > -- > View this message in context: > http://forum.world.st/About-Documentation-Teach-Don-t-Tell-Steve-Losh-tp4706413p4706603.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >
