Date: Fri, 30 Dec 2011 17:03:39 +0100 From: Polytropon <freebsd@edvax.de> To: David Jackson <djackson452@gmail.com> Cc: freebsd-questions@freebsd.org, Robert Bonomi <bonomi@mail.r-bonomi.com> Subject: Re: FreeBSD Kernel Internals Documentation Message-ID: <20111230170339.6d6af931.freebsd@edvax.de> In-Reply-To: <CAGy-%2Bi-m7hUfrUPKaG6FAiv8cor6%2BWXUW-OwWA=uOAt0yDToag@mail.gmail.com> References: <CAGy-%2Bi-NN_SOYrrE6WgHyCBa5VzFexwT_C9UYhO3GyjvfsxpAA@mail.gmail.com> <201112300604.pBU64dqB069626@mail.r-bonomi.com> <CAGy-%2Bi-m7hUfrUPKaG6FAiv8cor6%2BWXUW-OwWA=uOAt0yDToag@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 30 Dec 2011 10:22:31 -0500, David Jackson wrote: > Of course, those best able to document are those who wrote it in > the first place, since they already know how it works. A fact seems to be: "Modern" programmers don't bother with documenting, or coding guidelines, or style or other things that "slow down" development. This attitude isn't new in general, as it has been done that way even in IT dinosaur times: There are COBOL programs still running, and nobody knows _why_ they are running and _how_. If someone had written usable documentation at the time the program was created and maintained, skilled COBOL h4x0rs wouldn't be able to write the desired salary on the contract as _they_ wish. :-) But keep in mind: Writing code and writing documentation are two different things. There are people who are excellent coders, but bad writers. In some teams, you'll find code writers and doc writers separated, but working together. This approach isn't free of problems, but also seems to work. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20111230170339.6d6af931.freebsd>