![]() I think it is the Mix, that differs a good documentation, from a “bad” one. Some are reading PDF´s, some are using the Helpfunctions and some are getting new inspirations, on what to achieve with the software (or the solution for a current problem) by listening to relevant Podcasts, looking some Videos, or doing some lessons from the Inside-Program or similar. With this, they are both offering their information in different ways, and everybody is able to get the informations he needed to use the software in his/her favorite way. They have a similar bouquet of different sources of informations like Devonthink, with additional Podcasts, Videos or their “Inside”-Program and so on. I think Devonthink might be a good example for that, as they have a very good build in documentation, giving Hints and Tips on their functions, operating a good Forum where they reply to questions and are helping with problems, and where the user is also able to find help for a lot of reasons also with the search function, and who also are offering other means of information like their additional Handbooks, the TakeControl Editions, their Blog, their Q&A, their story of other users and so on.Īn other good example for a good documentation (from my point of view) is the OmniGroup. I think a good documentation is rather a bouquet of different sources for information. a copy of a document, made with carbon paper 2. ![]() I would also agree with that a good documentation today is not necessary a formal PDF or Printout. Answer (1 of 12): BCC stands for blind carbon copy and comes from the time. Of course there are a lot of people out there, who do not have to read a Manual (or at least think so) because they had used (or even developed him/herself) similar software before, and are thinking that they already know everything anyway, but this is not the regular user case if it comes to a good documentation. ![]() I am not sure, if there are really large differences between end-user and third-party-programmers, when it comes to identify a good documentation.įrom my site, a good documentation is one, where I could find an easy to understand explanation on every single function of a software (or any other “thing”), and how these functions are working together.Īs a documentation of a “regular” software (no Public Domain and so on!) would not contain anything an other developer would be able to use for his own projects (if it is not a software for developing software!) any other developer would have the same interest in reading an easy to understand description of all functions, like any other “end-user” would also do. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |