Re: (1)[0] ok but not 1[0]
- From: Uri Guttman <uri@xxxxxxxxxxxxxxx>
- Date: Thu, 13 Dec 2007 15:41:34 GMT
"FK" == Florian Kaufmann <sensorflo@xxxxxxxxx> writes:
>> What are your plans for this documentation? I'm sure people are
>> interested.
FK> I think I'll be writing for some weeks, maybe even months. I also have
FK> a job during the day :-). And since I am learning Perl, learning
FK> LaTeX, fiddling at my syntax notation the progress is not fast. But of
FK> course I'll put it under GFDL or something similar and put it on the
FK> net. Provided I am allowed to - the basics of my work are mainly
FK> "Programming Perl" and http://perldoc.perl.org/. I sometimes copied
FK> whole sentences. I fear I would break their copyright when I put my
FK> document under GFDL.
i applaud your attempt at this doc but i will wager it won't be nearly
as useful as you expect. there are dozens of perl tutorials on the net
and almost all are total crap and full of mistakes and bad writing. in
many cases the authors also were self taught and thought they can create
a better doc. turns out that writing technical docs (especially
tutorials) needs much more programming skill and tons of experience
which most of those authors don't have (or ever will have). some even
proclaim how smart they are and still fail badly. i have read many and
have posted shredding reviews on usenet in the past so go google for
some of them. consider that larry wall wrote 'programming perl' and is
considered a very good writer and of course knows perl very well. yet
some have problems with that book (note: it is NOT a tutorial or
beginner book). i will repeat it, tech writing is VERY hard and much
harder than anyone who hasn't done it realizes. it is by far harder than
programming as you have to write much more text than code, understand
the material far better than you need for coding and english (or any
other natural language) is full of ambiguity and nuance that is not
found in programming languages.
report back in 6 months for a proper review/shredding and you will find
all your time and effort will likely have been wasted. just watching how
you think in this thread tells me you are not qualified enough to write
another perl tutorial that will make any mark at all. nothing personal
but this comes from my experience reading amateur tech writing about
perl. i have also been a technical editor of 4 perl books as well as a
perl trainer and article author so i also have direct experience in this
area.
good luck, for you will need it. you don't realize how hard a task lies
ahead of you.
uri
--
Uri Guttman ------ uri@xxxxxxxxxxxxxxx -------- http://www.stemsystems.com
--Perl Consulting, Stem Development, Systems Architecture, Design and Coding-
Search or Offer Perl Jobs ---------------------------- http://jobs.perl.org
.
- Follow-Ups:
- Re: (1)[0] ok but not 1[0]
- From: Florian Kaufmann
- Re: (1)[0] ok but not 1[0]
- References:
- (1)[0] ok but not 1[0]
- From: Florian Kaufmann
- Re: (1)[0] ok but not 1[0]
- From: Florian Kaufmann
- Re: (1)[0] ok but not 1[0]
- From: Florian Kaufmann
- Re: (1)[0] ok but not 1[0]
- From: Ilya Zakharevich
- Re: (1)[0] ok but not 1[0]
- From: Florian Kaufmann
- Re: (1)[0] ok but not 1[0]
- From: Joost Diepenmaat
- Re: (1)[0] ok but not 1[0]
- From: Florian Kaufmann
- (1)[0] ok but not 1[0]
- Prev by Date: Re: split is not convinient
- Next by Date: Re: FAQ 4.58 How can I know how many entries are in a hash?
- Previous by thread: Re: (1)[0] ok but not 1[0]
- Next by thread: Re: (1)[0] ok but not 1[0]
- Index(es):
Relevant Pages
|
