Doctor Strange – Insights into Technical Documentation

by Marion Knebel on November 02, 2016

What is the connection between a movie based on a comic and technical documentation? You might think there is none. But on Saturday I was delightfully surprised to find that Dr. Strange is an advocator of good documentation. Last Saturday was marvel-lous.

WARNING: DANGER OF SPOILERS!

WARNING: DANGER OF SPOILERS!

This blog article may contain spoilers.
Spoilers may ruin your movie experience and potentially result in physical retaliation against the author of this article.

Just a joke. This article will of course not contain any major spoilers, that is, we will not disclose any details that are relevant to the story or ending of the movie. The good guy wins, the bad guy loses, that much is for sure anyway.

I digress. Back to technical documentation. In the movie, there is a secret book in the library that describes some rituals with the potential to shatter the world, including some tempering with time and other dimensions. You know, stuff that sorcerers do on an average day. The hero starts reading and immediately goes into action – without reading the instructions until the end, of course. Just before something really bad is about to happen, he is stopped by his tutors. They warn him about the dangers ahead and ask if he hasn’t read the warnings. Doctor Strange answers that he didn’t get so far and why are the warnings placed at the end anyway? In other words, had the author consulted with a technical writer, the warnings would have been placed where they belong: before the steps that potentially wreak havoc.

https://youtu.be/HSzx-zryEgM

Thank you Doctor Strange for the entertaining introduction into well-structured procedures.

On a side note: The villain tempered with the rituals as well and did not read the warnings either. However, who knows how the story would have ended if he had ...

 

Image source:

Gefahrzeichen © Reeel. Fotolia.com

Add new comment

Your email address will not be published.

You might also be interested in

iiRDS for the documentation of technical standards

by Patrick Schedlbauer on September 30, 2021

The iiRDS standard makes documentation smart – so it can be made available on portals, apps and data glasses. Case studies in the field of mechanical engineering are very often mentioned in connection with iiRDS – for example, the scenario of the service technician who uses an end-device to scan an error code on a machine that needs repairing and then receives a snippet of information on the display showing how to fix the problem. This article is about the extensibility of the iiRDS model in the automotive sector. more...

Creating surveys with Microsoft Forms - Part 1

by Lea Sophie Ladiges on August 30, 2021

For technical communicators, it is not always easy to understand the needs and tasks of the target groups for which we write technical documentation or develop technical solutions.

If your company uses Office 365 , you can use Microsoft Forms to quickly create electronic surveys. Your target audience only needs a few minutes to answer the questions, and you gain valuable insights for your projects. more...