![libreelec raspberry codec license libreelec raspberry codec license](https://pbs.twimg.com/profile_images/875848642380410881/P-adTw-i.jpg)
Which sounds harsh, but is far more efficient for everyone involved. You can also directly put the costs of this work against the customer, rather than eating it via the comprehensive wargaming scenarios mentioned above. Which cycles back to the second bullet above, where you have the opportunity to provide information that steers customers in the right direction, addressing potential issues preventatively rather than playing damage control if their use wasn't completely aligned with the documentation they blindly followed. Directly supporting them during their implementation can be more effective than them relying on generic documentation, since you can provide more contextually relevant details/instructions/direction. Which can either be using the product they may be familiar with, or suggesting a different one that's more appropriate that they may not have thought of. Which provides the chance for you to truly evaluate their situation and provide a more considered response that takes into account their use/circumstances. A corollary to the above - poor documentation trains your (potential) customers to just reach out directly and have a conversation about it. But not doing so while providing otherwise expansive/comprehensive documentation may lead to a false sense of understanding from your customers such that they write you off when your product would have in fact been a good fit. Wargaming out every possible contingency ahead of time would both be extraordinarily expensive, and result in documentation that would overwhelm the people using it. I could see this being a negative in this industry - Feature X may be fine to use, but introduce intermittent instability if used for extended periods of time simultaneously with Feature Y, which can be compensated for via Z but doing so shortens expected lifespan by 30%. The more expansive your documentation, the less dependent your (potential) customers will be on actually talking to you when evaluating if your product is fit for their use. Harder to weasel out if things are clearly documented. Poor documentation can act as a form of liability insurance - if someone uses a feature and things get weird, you can claim their use is out of spec. The more precise your documentation, the more stringent your customer's expectations become.
![libreelec raspberry codec license libreelec raspberry codec license](https://www.techilife.com/wp-content/uploads/2021/02/LibreELEC-vs-OSMC-1-e1612852646656.png)
![libreelec raspberry codec license libreelec raspberry codec license](https://www.avanzada7.com/en/imagen-producto/3-g729codec.jpg)
Which makes it both easier for competitors to strategically outcompete you, as well as counterfeiters to more accurately counterfeit your chips. The more comprehensive your documentation, the easier it is for your competition to get a complete read on your product and it's capabilities. Poor documentation can be as much an asset as a liability, depending on your perspective.