Lately people are asking me about my job, and in general I can say what information developers are doing and what kind of products we provide.
But, my everyday job looks not fascinating at all.
So, imagine you are said to write the documentation about some great tool or application the engineer have made, and here the technical writing process:
Step 1. Ask the engineer how the damn thing works.
Step 2. While listening, nodding.
Step 3. Crickets.
Step 4. Deafling silence.
Step 5. Tumbleweed.
Step 6. Just start writing something. Anything.
Step 7. Give this something to the engineer.
Step 8. Watch engineer become upset at how badly you've missed the point of everything.
Step 9. As the engineer berates you, in between insults he will also throw off nuggets of technical informtion.
Step 10. Collect these nuggets, as they are the only reliable technical information you will receive.
Step 11. Try like hell to weave together this information into something enlightening and technically accurate.
Step 12. Go to step 6.
But, my everyday job looks not fascinating at all.
So, imagine you are said to write the documentation about some great tool or application the engineer have made, and here the technical writing process:
Step 1. Ask the engineer how the damn thing works.
Step 2. While listening, nodding.
Step 3. Crickets.
Step 4. Deafling silence.
Step 5. Tumbleweed.
Step 6. Just start writing something. Anything.
Step 7. Give this something to the engineer.
Step 8. Watch engineer become upset at how badly you've missed the point of everything.
Step 9. As the engineer berates you, in between insults he will also throw off nuggets of technical informtion.
Step 10. Collect these nuggets, as they are the only reliable technical information you will receive.
Step 11. Try like hell to weave together this information into something enlightening and technically accurate.
Step 12. Go to step 6.



