Tag Archives: Technical Writing
In the movie Office Space, Tom Smykowski (played by Richard Riehle) writes technical manuals for the software company. His job as a technical writer becomes a point of discussion in the film, particularly when he tries to justify his role in the company by explaining that he takes the specifications from the customers and brings them to the software engineers.
If you’re a technical writer, you’ll relate to Tom’s dilemma. For Tom the struggle wasn’t the nature of his job, rather how to explain the value of his writing activities during HR reviews. So how can you approach this?
10 Signs you have a technical writer’s personality
If you’re thinking of moving into tech docs, here’s a list of things to consider.
There’s no priority to the items I’ve listed here. For me, these are some of the traits you’ll need to enjoy a career in technical writing.
If you’re considering a career in technical writing, specializing in AI documentation offers promising career opportunities. I’d recommend that you create 30-day plans to go deep into the technologies to give yourself and edge over other writers and carve out a lucrative career in this area. Here’s how to get started.
API documentation skills are increasingly in demand as businesses looked to API-ify their product lines.
If you’re interested in learning about APIs from a documentation perspective, I’d suggest you connect with the following tech writers on Twitter.
An Audience Analysis questionnaire is a set of questions designed to understand the target audience for a technical document. It helps writers tailor the content to the needs, interests, and knowledge level of the readers.
In this week’s technical writing tutorial, we look at how to write a user story. You can use these guidelines and checklists to refine your user stories, expand the material to help your readers understand the scenario, allow developers to code the requirement, and testers to ensure it meets the acceptance criteria. Let’s get started.
Who do you write for? This is a problem for many technical writers, especially if you don’t get to meet or interact with your readers. Essentially, you’re writing in the dark. But, that doesn’t mean you can’t improve the usefulness of the documents. Far from it. Technical Documents: How to be more accurate For example, […]
In December, I looked at the daily rates for technical writers and others in the tech comms industry. At the time daily rates for technical writers are down to $30 per hour in some places in the Bay Area. However, maybe things are starting to turn around. In Ireland (Euro HQ for most US IT companies) Google has announced 150 new jobs, many in technical roles. So, is the tide starting to turn?
How much time do you spend writing every week? Remember, you have 37.5 hours (I know!) for technical writing every week, but how much is actually spent writing? When I say writing I actually mean developing content, so this includes illustrations, diagrams, publishing etc – whatever goes into the final deliverable.
- 1
- 2