> But how can you call documentation wrong without seeing the source code? Very easy - by observing reality, and how it matches to what's documented > And if

> But how can you call documentation wrong without seeing the source code? Very easy - by observing reality, and how it matches to what's documented > And if the direct source is wrong, how could the secondary source then be right? In exactly the same easy way - by observing and documenting reality. For the same reason this is a second primary source, not a secondary one > Sounds to me like developer or designer arrogance is at play here, when they should be questioning the correctness of their own understanding. Good albeit slightly misdirected advice, we have a great case of misunderstanding pretty trivial things that lead to trivial questions and faulty personality assessment