: How can I describe technology while avoiding problems with scaling? Worldbuilding chat has pointed me to this stack because it's less about defining the technology and more about how to express
Worldbuilding chat has pointed me to this stack because it's less about defining the technology and more about how to express these definitions in a relatable and realistic way.
A pretty frequent occurrence when working with fictional technology is that when describing what the tech does and how it works, the author messes up the scale of the underlying technology or what it is capable of. This can happen in multiple ways (all examples are purely fictional):
The author describes near future technology with ludicrous numbers, which actually are on the other end of the power bell curve. the author may, in 2001 describe a computer in the 2050s whose power is actually closer to something from the 2020s. The opposite also happens: the components from the machine actually are much stronger than what's possible at the time.
The author describes a machine that actually is woefully underpowered for what it is said to be capable of. For example, blowing up a meteor the size of Texas with a nuke buried 800 feet deep.
The author describes a machine that actually has much more energy than needed for the job. They mention "a 1 Kt bomb, big enough to destroy the empire State building", but such a bomb would actually take out everything 5 blocks around the empire state building as well.
The author has a concept that's scaled well at the time it's introduced to the story, but when used later on, it either scales poorly or not at all. An example would be a martial artist taking of weighted clothing as a powerup, but he keeps doing it even when he's not even hindered by the clothes anymore.
Note: I'm talking about purely numerical issues with scaling, not the technology itself becoming outdated because new tech is invented. I'm not talking about "cassete recorders in space", I'm talking about "A spaceship to the moon with the power of a bottle rocket".
Assuming you already have your technology worked out concerning what it has to do, how do you go about describing the tech to a reader without pulling potentially knowledgeable readers out of the story when your numbers don't add up?
More posts by @Twilah982
: No, I know of several fantasy authors who not only use citations without the philosopher's name, but attribute the quotes to a fictional author who is part of their world.
: Where to publish essays about a life stories for personal development? I had a few experiences of things which I learned from some amazing people in my life. I would like to share some of
2 Comments
Sorted by latest first Latest Oldest Best
One good trick is to choose a point of view characters who is at the low end of technical competence. That way your other characters will talk down to them (and the reader), avoiding technical descriptions which involve numeric and scientific details.
A cub reporter, the ship's recreation officer, or a hobbit from a backwards and far-off land... these are all great point of view characters who can work their way into the action without ever having to really understand what is going on or how things work.
The weapons chief paused, obviously calculating the explosive force needed to vaporize an asteroid of our target's size and density. I watched her lips moving as she silently did the heavy math. Then, realizing that I was waiting for an answer and recognizing the kind of answer I was looking for, she paused, smiled, and said, "It will have to be a really big bomb, but we can do it."
If you've worked out the tech, why haven't you worked out the scale? Isn't that part of "working out the tech"?
Just coming up with the idea of "a rocket that goes to the moon" isn't sufficient. You have to come up with how it goes to the moon. If your story is meant to be realistic, then you have to do enough hard-science research to determine how a rocket could actually get to the moon. You need to understand thrust, weight, the layers of the atmosphere, velocity vs. vacuum, orbits, and so on.
If your story is fantasy (relying on magic, for example), then you still have to cover the mechanics of getting to the moon, and your magical system has to be logical to a certain extent. (This is what I call the Heroes Power Conundrum. The show Heroes had people developing abilities like being able to heal from any wound, or flying, or turning invisible. But those gifts never seemed to require power. If the cheerleader grew back a toe, the energy to create that toe had to come from somewhere. She should have been constantly eating cheeseburgers to fuel her healing.) So just "casting a spell to put the rocket on the moon" is insufficient. You have to establish how such a spell is learned or created, where the magic comes from, who can use it, if there's backlash, et cetera.
The short answer is, to avoid problems with scaling, figure out how the tech would really work, or as close to it as possible. If you put a bomb in a building, do research on how much C4 you need to take out a building of that size, or how much more damage your chosen amount of C4 would do. And so on.
Terms of Use Privacy policy Contact About Cancellation policy © selfpublishingguru.com2024 All Rights reserved.