Professional Documents
Culture Documents
I am back!
To become a technical writer I find some tutorials. For example, [**Googles Technical Writing
Courses**](https://developers.google.com/tech-writing) is a good starting point. There are different
parts for Students, Facilitators, Doc Resources, and some pointers on how to Become a Technical Writer
at Google.
It seems to me that every writing course for a technical writer is for a developer who is willing to change
career. I am not a developer or programmer and will never become one. At least Mirko says.
All the time I tried to learn how to write API documentation, this is what Mirko needs for his company.
So, I tried to skip some steps and immediately start to write serious stuff.
When the newspaperman asked Ante Kostelić, father and a ski coach of Olympic gold medalists Janica
and Ivica what is your secret, how did you train your kids to become champions? He just said. "There are
10 Gods commandments in training. You follow not 8 or 9, you follow all 10!"
So, Mirko said to me: "Just write. Whatever you write is better than thinking and overthinking."
Now I am writing about my experiences from day one on the path to becoming a full technical writer.
So the plan is to write about steps I am making or about to make. This is more of a process of learning
and gradually writing more and more technical stuff. Hopefully, the end is to be a full technical writer.
The first document I wrote was Instructions for new user account registration, for the local Tennis
association.