3 ms·
This is solid advice. In large, technical companies you'd be surprised at the number of technical writers that aren't actually technical. Having someone that ac
by snide 4y ago
This is solid advice. In large, technical companies you'd be surprised at the number of technical writers that aren't actually technical. Having someone that acts as a source writer, rather than as an editor for developers that are quickly rushing past the documentation requirements is a game-changer. The best technical writers I've worked with were always folks who understood programming and could write the docs from experience.
I also find most technical documentation teams to be a lot more chill and flexible. Most of them have excellent team-minded work styles.
How to get started in this field? You can't throw a stone without hitting an OSS project that wouldn't want help with its docs. It's a great way to build up a network and some Github activity.
- noduerme 4y agoThird this. One of the companies I develop for hired a technical writer to translate large pieces of our code into user-friendly manuals. She isn't a coder but she's a good writer and has a knack for finding problems and asking questions from the user's perspective. Most importantly, she's intellectually curious. She sort of fell into the position by being a regular employee who raised a lot of good questions about the old software as it existed. She's paid well by the client, picks her own hours and problems, has a hand in suggesting new features, sends me lists of questions and I answer as I do... in extreme detail and with tons of edge cases. She then just keeps testing things out and distills my technical babble down to the manuals that are used to train the managers.