Re: CW X 10.1++ ... let's start a pool

> I'm not advocating you part-time for tech pub writing pages and pages
> of docs every week. You encounter a problem you think is terrible and
> poorly documented. You see lots of other developers in the same boat.
> You solve it. You doc your solution in a few pages on the web.

Make up your mind. If I did as you suggest, I would be writing pages
and pages a week. Seriously. I'm probably stumped by inadequate
documentation at least 60% of the time I try to do something I haven't
done before. Ran into it earlier tonight as a matter of fact.

> Many other enthusiastic developers do the same. Where's the crime?

It's not a crime, it's just not the right solution IMO. At best it
results in documentation scattered across thousands of web sites. At
worst it's going to result in documentation scattered across thousands
of web sites and not all of that documentation is going to be correct.
I've seen a lot of people post the code they use to solve a problem and
it was more of a hack than a correct solution. Who wants to wade
through hundreds of hits in a Google search trying to find solution
he's confident is correct?

It doesn't escape me that you have no valid argument for my position on
Apple's documentation. Instead, you just ignore valid points and launch
into an irrational personal attack on me, claiming I'm some kind of bad
person for not doing their job for them. Okay, fine, I'm a terrible
person.

> Why can't you do that, especially when you say how much you love -- l o v e
> -- MacOS land. Ironically enough you are willing to spend many hours a week
> writing gigantic posts complaining, yet again, about the problem.

Do you think Apple's documentation is complete and up-to-date? If not,
do you write them and encourage them to do better? Or do you think
calling me names is more productive?

> By crafting me a huge response, in your last post, that is simply a
> large excuse out of any -- even a small -- contribution,

Nonsense. Let me know when reality holds value for you.

> I think you are a whiner. Not a squeaky wheel. And a hypocrite. Or simply
> you are not as dedicated and passionate about MacOS as you claim.

Thank you for your personal value judgements. How do *your* posts
improve the state of Mac OS X docs? What you fail to take into account
in your flawed logic is that I feel very strongly that Apple should
take a stronger role in this. I don't think it's my job or your job or
the job of any group of developers, but I *do* think that the more we
take up their slack and make excuses for them the less likely they are
to do better. Even people I know inside Apple think Apple should be
doing a better job and all you can do is criticize me.

FYI, I *have* written and posted web pages because I saw a serious void
in the docs. Apple took those pages and turned them into a tech note.
Why should I be writing Apple's tech notes for free? If I were trying
to get Chevrolet to address a defect in one of their cars would you
criticize me for not getting out my toolbox and fixing people's cars
for them? Your position that I should be documenting Mac OS X when I
see a problem is just absurd. At best I should be reporting problems to
Apple (which I do -- I reported one tonight as a matter of fact), but
posting web pages to document Mac OS X? Ridiculous.

Larry

.

Relevant Pages

  • Re: CW X 10.1++ ... lets start a pool
    ... You see lots of other developers in the same boat. ... Ironically enough you are willing to spend many hours a week writing gigantic posts complaining, yet again, about the problem. ... documentation for Mac OS X so Apple can save the cost of hiring people ... By that I mean I should be able to figure out how to use any technology and any API using documentation they provide. ...
    (comp.sys.mac.programmer.codewarrior)
  • Re: programming job market in bay area in US
    ... certainly not enough to be able to debug my translator by knowing what ... any of a wide range of different things, from simply writing utility ... Would any of that qualify as "systems programming"? ... drafts of the documentation, then I wrote all the rest of the ...
    (comp.programming)
  • Re: The rise and fall of linux
    ... > Have you ever considered picking a chunk of outdated ... > domumentation and writing an improved replacement? ... Linux including and especially writing documents. ...
    (alt.linux)
  • Re: Tuning for PostGreSQL Database
    ... Anything that PostGreSQL reads should wind up in the cache? ... As I said before, there's really no good documentation, except the ... Short of writing better documentation, that's about all I can tell ...
    (freebsd-performance)
  • Re: Why has the Metrowerks sign been taken down?
    ... Apple could have invested, let's err on the side against Larry's, ... > leveraging effect wrt Apple documentation, dev tools and OS bug fixes. ... dev bugs and engineering probably have ...
    (comp.sys.mac.programmer.codewarrior)