Laer Carroll
LaerCarroll.com
- Joined
- Mar 3, 2009
- Messages
- 1,313
Writers of futuristic fiction must “invent” the futuristic technology in their stories. It takes much skill to make it convincing, yet spend few words on it so that it stays in the background. Otherwise it would take attention from people and their activities which are the main focus of stories.
Here are some tips drawn from my experience as an aerospace software and systems engineer.
Separate the WHAT and the HOW of future tech. In engineering this is known as separating requirements and design. You first say what you want a new product to do and completely ignore how it can do it. There are whole books on this “requirements engineering” process. These include long checklists of capabilities, such as how fast (or slow) a new thing works, how much energy it can use and for how long, and much more. If the product will be physical, requirements can include weight and size.
How the product works is only looked at when the “what” is OK’d by all “shareholders” - everyone concerned with the product, such as financiers, marketers, and users both individual and collective. You the writer are lucky; you don’t have to spend hundreds or thousands of hours working this out. You just describe the tech and its workings - briefly! - and go on with story.
STEAL where you can. Engineers in every field nowadays never invent something from scratch if we can re-use some other product or combination of products suitably modified. If some off-the-shelf product is good enough (as defined by requirements) we use it straight away. This is not just cheapness. OTS products usually have had long and rigorous testing both in the lab and by users. They are also available in large quantities cheaply.
Sci-fi writers, of course, have a big selection of OTS products. Hyperdrives, for instance, are available in many kinds and capabilities! You may have to do some minor “mods” so that yours doesn’t seem too imitative. But don’t waste too much time on this. In engineering one of the oldest principles is “If it ain’t broke, don’t fix it.” And “Better is the enemy of good-enough.”
Think SYSTEMS. Technological products never exist in isolation. Your future tech will seem more convincing if you include a few mentions of the other tech which makes it possible. Cell phones, for instance, exist because of web-works of cell towers. GPS car dashboard products work because of satellites orbiting the planet.
Most of these systems work in the background and require no more than a mention, if that. But they can also provide plot pivot points if, for instance, a supporting system breaks down or (better!) is sabotaged.
Think LIMITS. All tech has limits. Your blaster will be more convincing if you have to swap batteries during a gun fight, or find that bad guys have emptied your weapon. Your teleporter will seem more real if your character must switch from a local to a national “line.” Or be delayed if the ground-to-orbit line goes offline for maintenance - possibly allowing your main characters to meet while waiting.
That’s it. I could go on. But a story calls! Add your own suggestions below.
Here are some tips drawn from my experience as an aerospace software and systems engineer.
Separate the WHAT and the HOW of future tech. In engineering this is known as separating requirements and design. You first say what you want a new product to do and completely ignore how it can do it. There are whole books on this “requirements engineering” process. These include long checklists of capabilities, such as how fast (or slow) a new thing works, how much energy it can use and for how long, and much more. If the product will be physical, requirements can include weight and size.
How the product works is only looked at when the “what” is OK’d by all “shareholders” - everyone concerned with the product, such as financiers, marketers, and users both individual and collective. You the writer are lucky; you don’t have to spend hundreds or thousands of hours working this out. You just describe the tech and its workings - briefly! - and go on with story.
STEAL where you can. Engineers in every field nowadays never invent something from scratch if we can re-use some other product or combination of products suitably modified. If some off-the-shelf product is good enough (as defined by requirements) we use it straight away. This is not just cheapness. OTS products usually have had long and rigorous testing both in the lab and by users. They are also available in large quantities cheaply.
Sci-fi writers, of course, have a big selection of OTS products. Hyperdrives, for instance, are available in many kinds and capabilities! You may have to do some minor “mods” so that yours doesn’t seem too imitative. But don’t waste too much time on this. In engineering one of the oldest principles is “If it ain’t broke, don’t fix it.” And “Better is the enemy of good-enough.”
Think SYSTEMS. Technological products never exist in isolation. Your future tech will seem more convincing if you include a few mentions of the other tech which makes it possible. Cell phones, for instance, exist because of web-works of cell towers. GPS car dashboard products work because of satellites orbiting the planet.
Most of these systems work in the background and require no more than a mention, if that. But they can also provide plot pivot points if, for instance, a supporting system breaks down or (better!) is sabotaged.
Think LIMITS. All tech has limits. Your blaster will be more convincing if you have to swap batteries during a gun fight, or find that bad guys have emptied your weapon. Your teleporter will seem more real if your character must switch from a local to a national “line.” Or be delayed if the ground-to-orbit line goes offline for maintenance - possibly allowing your main characters to meet while waiting.
That’s it. I could go on. But a story calls! Add your own suggestions below.

