software manual

Lost User

Double-click1 on the program icon to run the application. The application is easy to use so no further instructions should be necessary. 1 If you don't understand the term 'Double-Click' please step away from the computer.

___________________________________________ .\\axxx (That's an 'M')

Super Lloyd

Ho my god, it works for our application too!!! :-D

A train station is where the train stops. A bus station is where the bus stops. On my desk, I have a work station.... _________________________________________________________ My programs never have bugs, they just develop random features.

PIEBALDconsult

"It has only one button and we press that before it leaves the factory." -- Dilbert (?)

Mycroft Holmes

kdgupta87 wrote:

but i will never write a 1 page software manual

Good luck with that, a senior dev may get away with it if there is someone to delegate to but a junior will be stuck with it. While I have a similar attitude I'm a grumbly old bloke who has done it before and can get away with it. And yes doco is difficult, kudos goes to all those technical writers out there.

Never underestimate the power of human stupidity RAH

Lost User

One size fits all :)

___________________________________________ .\\axxx (That's an 'M')

RaviBee

Yes, writing technical documentation is hard. Writing a user's guide is even harder. It helps to enjoy wanting to write and knowing your audience. It also helps to know how to spel. :) /ravi

My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com

Lost User

:laugh: My 5 too.

Regards, Koushik. Most people never run far enough on their first wind to find out if they've got a second. Give your dreams all you've got and you'll be amazed at the energy that comes out of you.

Mark_Wallace

_Maxxx_ wrote:

Double-click1 on the program icon to run the application.

heh. With our stuff, it's: 1. Edit thirty-odd text files to configure the applications, messaging systems, data-sources, etc. 2. Set up your data sources to feed to the addresses entered into nine of the thirty-odd text files. 3. Configure the internal data redistribution system with the provided tools and text files. 4. Lose track of what you've put in which text file, and start over -- if you can remember where all the text files are. 5. Edit yet more text files to configure the tools that restructure the data from the different data sources to make it compatible, bearing in mind that if you make any mistakes, nothing at all will work (or all your data will be silently corrupted -- option A is better). 6. Type the "Go" command and the long list of its parameters on the command line and hit Enter. 7. Ignore the smoke. 8. Wait a few days, because it can take that long, then call our help desk and request a technical support guy on-site. I suppose I could stretch it out to fill a page, but why bother?

I wanna be a eunuchs developer! Pass me a bread knife!

Ravi Sant

You need some help from here

NormDroid

And it well be out of date by the time you finished it.

Software Kinetics - The home of good software