Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:
You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.
I can assure you in the support arena we regularly read documentation, in fact before selecting a product for use I will read the documentation and form an opinion about the quality of the application, many times before even trying it.
If ever you try to sell an app online plenty of screenshots and a good feature guide will do you more good than any fancy sales pitch (major software houses please take note).
Badly composed documentation suggests poorly written software. So yes send it to Bob!
For the next week, I'm writing documentation of stuff I've developed. It seems to me that this task would be better handled by off-shoring, to, say, India. No-one ever reads documentation, so the quality and content are irrelevant - so long as the documents are formally correct, so as to get FDA approval - who cares?
Leave a comment: