4 ms·
"Your software is not working if it doesn’t exactly match its documentation." Not true. Documentation is not always updated. And many times, if not every time,
by s73v3r 11y ago
"Your software is not working if it doesn’t exactly match its documentation."
Not true. Documentation is not always updated. And many times, if not every time, the requirements documents the clients give are often flat out wrong. So you could build the software to the requirements, and end up with something that doesn't meet the client's needs.
"Documentation and Code Quality are some of the most important features."
However, these take a backseat to working software.
- kuschku 11y agoYour software is not working if all the third party services that depend on the API you provide are broken because you changed your API, or because your documentation is wrong. You can work without documentation or without stable implementations if you control all the endpoints and ensure they always have the latest version (like mobile apps, web apps, etc). But if you can’t, you have to remember that every API version you’ll ever provide will have software using it, and you won’t be able to EOL the support for that version.