On Wed, 2007-08-01 at 00:52 -0700, UNIX admin wrote: > > Its about communication and advocacy - its about > > making sure developers > > understand the process of contributions and the > > rationale behind it - > > stop hiding under layers upon layers of documentation > > - documentation > > that is 9/10 filled with waffle. > > You don't like reading documentation, or what? What do you think, that > development and/or engineering is a partisan, guerilla coding process? > > Sun documentation has always been one of the biggest incentives to > take and implement Sun technology. What good is an "awesome" > technology that there is just no documentation for? And, I have to ask > myself how awesome is it really if the documentation is nonexistant, > boils down to a couple of READMEs or HOWTOs, or just plain sucks. > Awesome products start with (often just as awesome) documentation.
I'm talking about the guide for example to using BFU; I condensed it down to a small post on my blog - from something that went on for pages to something that no bigger than a postage stamp. As for the official documentation, it makes assumptions on the users part - one assumes that if they just want to get something working, they don't want the life story of the product or the programmer who wrote it, but merely a step by step instruction on how to get a specific thing working. Matthew _______________________________________________ opensolaris-discuss mailing list [email protected]
