Tag Info

New answers tagged

5

Are there things like these and I'm missing them? Things that do the same job as I am describing? There is an excellent book called The Architecture of Open Source Applications that provides detailed descriptions of a variety of high-profile open source software projects. However, I'm not sure if it exactly fills the role you're imagining, because I ...


4

Because there are far more open-source programmers than open-source technical writers. Documentation takes maintenance and time to keep up to date. The more bulky the documentation, the more it takes. And documentation that isn't in sync with the code is worse than useless: it misleads and conceals instead of revealing. A well documented code base is ...


14

The dry, harsh truth? Documentation is not made because projects can do without it. Even open source projects often face stiff competition. Most of such projects don't start with large shoulders, they start off a bright idea, often a one man bright idea. As such, they can't afford the time and costs of hiring human documentors, even if they offered to ...


-1

Besides being extra effort, some open source project are crippling their documentations on purpose, in order to get freelancing jobs for their maintainers (to implement something, or to hold trainings). Not only they don't have code overview, but their API and tutorials are bad or missing lots of things. Just to name one quite popular : bluez. Good luck ...


59

Because it's extra effort to create and maintain such a document, and too many people don't understand the associated benefits. Many programmers aren't good technical writers (although many are); they rarely write documents strictly for human consumption, therefore they don't have practice and don't like doing it. Writing a code overview takes time that you ...


7

Overview documents such as you describe are rare even on commercial projects. They require extra effort with little value for the developers. Also developers tend not to write documentation unless they really need to. Some projects are lucky to have members who are good at technical writing, and as a result have good user documentation. Developer ...


0

Note that the pseudo-code in wiki is not practical. It is written to undestand. If an array is [0,0,0,1] pivot is 1 and other elements are less than the pivot, then swapping(t <-- a, a <-- b, b <--t) works as t <-- a, a <-- a, a <-- t. In this case swapping works nothing. If an array is [4,2,1,3] then [4,2,1,3] --> [2,4,1,3] --> [2,1,4,3] ...


2

The body of loop you've written is entered n+1 times (i from 0 to n), after that the variable i is incremented again, it's value now becomes n+1. Then it is compared to n ( i <= n ), this test fails and the body of the loop is skipped.



Top 50 recent answers are included