Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Post History

50%
+0 −0
Q&A Good idea to describe the heist place before the heist begins?

I think a good rule of thumb would be: Up-front, in preparation, the story can characterize one or two major challenges the heist will need to overcome. That's enough to whet the reader's appetite...

posted 10y ago by Standback‭  ·  last activity 4y ago by System‭

Answer
#4: Attribution notice removed by user avatar System‭ · 2019-12-12T20:06:02Z (over 4 years ago)
Source: https://writers.stackexchange.com/a/9695
License name: CC BY-SA 3.0
License URL: https://creativecommons.org/licenses/by-sa/3.0/
#3: Attribution notice added by user avatar System‭ · 2019-12-08T03:14:51Z (over 4 years ago)
Source: https://writers.stackexchange.com/a/9695
License name: CC BY-SA 3.0
License URL: https://creativecommons.org/licenses/by-sa/3.0/
#2: Initial revision by (deleted user) · 2019-12-08T03:14:51Z (over 4 years ago)
I think a good rule of thumb would be: Up-front, in preparation, the story can characterize **one or two major challenges the heist will need to overcome.**

That's enough to whet the reader's appetite and to build anticipation. It's also enough to allow you to write very quick explanations _while_ the action is happening. If we know the bank is patrolled by robotic guardian leopards, then you don't need to explain ahead of time how the team is going to sneak in through the decorative fountain and then remotely detonate a catnip distraction. For these smaller details, you can shed light on the explanations as you go along with the actual action:

> We were leaking water out of our boots, but it had worked - the robo-pussies never went near the water, and hadn't noticed us. Yet.
> 
> "You ready, Brenda?" I muttered. She was taking her sweet time opening up the watertight bag. She didn't answer immediately, and for a moment, I was afraid the bag had sprung a hole, and we were all dead meat. But then she breathed out, and raised the detonator out of the bag. "High and dry," she said. "Hope the pussies like their catnip."

...and so on.

For heist scenes, the reader generally is willing to accept that he won't be privy to the full plan before it goes down. If he had to wade through all the details when the protagonists do, they'd be ridiculously boring, and then there'd be a big long heist scene which'd be boring because now the reader knows what's going to happen. So revealing the details as you go is a great way of avoiding a huge infodump, and it does a good job of conveying the suspense, the meticulous planning, the careful consideration of branching possibilities - just as they become relevant.

What you _do_ need to do is have those major obstacles in place already, familiar to the reader - otherwise you'll have your characters climbing out of the fountain and then stopping for a long explanation of robo-leopards.

#1: Imported from external source by user avatar System‭ · 2013-12-11T19:19:38Z (over 10 years ago)
Original score: 2