Re: Docs
Re: Docs
- Subject: Re: Docs
- From: Georg Tuparev <email@hidden>
- Date: Fri, 24 Aug 2001 12:45:48 +0200
Bertrand,
On Friday, August 24, 2001, at 11:01 AM, Bertrand Mansion wrote:
>
> They are so consistent, that quite often I just think "hmm, it should
>
> be
>
> a method that does this and that", and I type doThis:withThat: and
>
> press the compile button, and I feel like there is a chance of 70% I
>
> will not get even a warning. Taking into account this consistency, and
>
>
Uhmmm, voodoo programming, this sounds quite interesting...
>
No. There is no voodoo programming. There is a programming by
coincidence, and unfortunately many people use this style, but no voodoo
here. What I was describing above is programming by intuition. To
develop intuition, you need a lot of practice, and a lot of thinking.
One should always ask question like "Why I am doing this", "Why Apple
folks done it that way" etc. pp. There are frameworks who help you build
intuition faster (the famous "aha" feeling), and what I was trying to
explain above is that Cocoa frameworks are very intuition friendly.
>
> With all due respect to some of the members of this list,
>
>
I don't see any respect here. What is the purpose of this list ? Help
>
'some
>
members' or all members of the list ?
>
Help yes, flame others work - not!
>
> the biggest source of confusion, is not the quality of the
>
> documentation, but the lack of good C knowledge and understanding of
>
> the basic object oriented concepts, as well as insufficient experience
>
>
You shouldn't have to look at the headers in order to understand the
>
framework and its behavior. This is only the evidence of a bad
>
documentation
>
or a bad implementation. Cocoa users suffers from a lack of
>
documentation,
>
not deficiency in C programming. Of course, we are unfortunately not
>
all of
>
us voodoo programmers, but you will teach us.
Again, one of these non Cocoa principle you might learn while studying
general programming technics is called DRY (Don't Repeat Yourself).
Rarely only technical writers (not only Apple's tech writers) a are the
people who cut the source. So these technical writers have to learn the
functionality themselves (and in most cases they do it from the headers)
in order to write documents. Unfortunately this brakes the DRY
principle, and the documentation is often out of sync. Therefore, not
only I, but many folks on this list will recommend you to consult the
headers.
Georg Tuparev
Tuparev Technologies
Klipper 13
1186 VR Amstelveen
The Netherlands
Mobile: +31-6-55798196
| References: | |
| | >Re: Docs (From: Bertrand Mansion <email@hidden>) |