|
Sc3pt1c4l wrote: What exactly IS a burn phone?
I think he means burner phone, which is a disposable pre-paid phone.
|
|
|
|
|
Yep, I think you are right. Might need a glossary then 
My burner is a safe cell and to another it's heat.
My booty is my stash and to another it's just - a bit of flash.
|
|
|
|
|
I'm guessing this snippet opens your first chapter. If so, I like the concept -- it's a great grabber.
In my opinion, this passage is a good first draft, but it's rough. Spend time wrestling over every line. Every detail counts. Think each one through. For example "It was well lit" was one of the "good reasons" to use the study room. But he doesn't look at the envelope until he goes out to the car. So that detail was unnecessary. Other details to reconsider:
* Don't know what a burn phone is. Thought it was a typo of some kind.
* The sentence starting "20 minutes later" is too long. Kind of a run-on. Break it up.
* The sentence starting "It was well lit..." has a few typos and needs to be re-written. ("all good reasons for he used it..." -- huh?)
* How did he know which of the "old gilded bibles" to choose? Was it marked?
* Took 10 minutes to memorize an address? And he's done this before, has he?
* He set a fire on a public street? And he doesn't want to be noticed?
But my bigger observation is that you're way too eager to reveal the back story. The fact that he's not a priest, the source of his nickname, the stuff with the CIA -- that should all come out WAY later. Eek out those details bit by bit; keep the reader wondering (not *confused*, but just "in the dark"). Those paragraphs sound like explanations to the publisher. Plus, they interrupt the narrative. Keep the action going. THAT'S what is compelling. His motivations should be a mystery until deep into a subsequent chapter.
|
|
|
|
|
Well, first of all, just a little typo that you missed:
"It was well lit, quite, and out of the way"
Other than that, I think you could use a more personal and detailed point of view for the main character. You have some good visual description, but don't forget the other senses! Try describing the tactile feel of things (the smooth, polished wood of the pews?), the scents in the air (candles?), the sounds ("quiet" says something, the soft murmur of private prayers says more). These kinds of things can really ground the reader and help them feel like they are experiencing the world through the eyes of the protagonist.
Keep in mind that this sort of writing isn't journalism, keep the exposition to a minimum, you aren't just telling a story you are building a world. For instance, instead of explaining his military background, how about a flashback to those days showing how he got his nickname? Don't be afraid to devote a whole chapter to that kind of thing. The general rule is show don't tell, the reader wants to experience the story not just be told what happens.
Good luck with your virtual murder 
modified 5-Aug-15 11:34am.
|
|
|
|
|
It certainly applies here. You could also take note of his preference for economy. Once we've seen the protagonist entering the parking lot we really don't need to be told that he parked. If he did something unusual like speeding round the lot on only two wheels then by all means tell us that but parking .. well, duh. And if the exact road he turned off is of no significance to the story at a later point, who cares? Similarly we can cope without being told that he opened a door to go into a room unless there's something about the door of note (it's locked, it's smeared with blood, it's got no handle, whatever).
Although I wouldn't advocate going to the present tense necessarily you should certainly modify your use of what Greek scholars would call the aorist; the absolute, single event, past. It is that which gives it the staccato feel which others have commented on. Use the imperfect and participles to give the sense of continuing action.
Here's my very quick rewrite of the first part as a guide to what I'm trying to say. You'll notice that I've cut out a lot of extraneous detail and a few logical errors (there's nothing about being well lit that makes the reading room ideal for him surely?) to keep the story moving. But even then I wouldn't be content to say this was the finished article. I'd expect to do at least one (and probably more) rewrite before I'd even consider letting an editor see it.
The burner phone in the Priest's hand buzzed with a new message as soon as he turned it on. It read ...
"As Elijah was taken to Heaven so we shall be. Praise be to God. 2 Kings 2:11"
Deleting the message and shutting down the power, he flipped the phone and removed the SIM card before flushing it down the toilet. The phone he would dispose of later in some stranger's trash.
Twenty minutes later he was pulling into the parking lot of the Archdiocese of Santa Fe Catholic Center, a typical brick church with thick mahogany doors and a steeple, a rectory, and the Bible study facility to which he was headed. In the reading room, sleepy quiet and out of the way (ideal for his purposes), he passed by the few people reading or working on laptops barely noticed. Amongst the collection of gilded Bibles and study guides against the back wall he selected a large King James and slipped out a plain envelope from the pages of 2 Kings 2. After hiding it in his coat and pausing long enough to deflect any suspicion he returned to his car.
|
|
|
|
|
Wow. Excellent advice. Thank you
If it's not broken, fix it until it is
|
|
|
|
|
Good point about economy of words, and the best way to do this is with compression. Packing a lot of meaning into a few words adds a lot of power and punch to the prose. Consider this opening sentence from William Gibson's Neuromancer:
"The sky above the port was the color of television, tuned to a dead channel."
In one short sentence, Gibson sets the scene, tone, and theme. We know we are in a port city, the weather is dreary and grim, and we get a strong sense of technological angst.
A lesser writer might have spent paragraphs describing that opening scene. Gibson did it in fifteen words and then immediately jumped into the dialog and action. That's very powerful, and doesn't give the reader a chance to lose interest.
Good editing is the art of removing words, not adding them. When you've done away with the unimportant stuff and have nothing left you can take out, that's when you're done. As the apocryphal quote goes, "I'd have written a shorter letter if I'd had the time."
|
|
|
|
|
You misspelled "quiet" as "quite". Sorry, my OCD acting up.
It's too long, with not enough motion. Why do I need all this info here and now. You could have established his "priest" persona more rapidly. All the detail just slows down the pace. Maybe at this point, you require the pace to be slow and methodical, but I don't sense that. Try saying all the same stuff in half the words. Concentrate on the scene, for versimilitude, or concentrate on the character's experiences. What does he think on entering the church. How does it affect him. Does it bring back memories? This will help you elucidate his past, which I assume you need to do, without requiring so much overt recitation of fact.
Don't spend too many words getting the geeky stuff right. Why not remove the battery and keep the phone? Why not leave the thing turned on and drop it in a dumpster (oops, that's Dumpster)? Why not toss it into the bay? The particular way he disposed of the phone either directly furthers the plot (like the police find it and run fingerprints), or it's irrelevant, in which case why waste words on it ("...disposed of the burner phone...". Too many words is a bigger problem for authors than not enough words. Don't worry, you'll fill your allotment of pages.
|
|
|
|
|
Thank you
If it's not broken, fix it until it is
|
|
|
|
|
Kevin Marois wrote: It was well lit, quite, and out of the way – all good reasons for he used it for his purposes.
I like it but one thing jarred me, I think you meant quiet not quite.
Have a good one.
|
|
|
|
|
But you have no objection to "all good reasons for he used it for ..."?
|
|
|
|
|
Message Closed
modified 18-Aug-15 15:39pm.
|
|
|
|
|
Maybe you could post some of your writings?
If it's not broken, fix it until it is
|
|
|
|
|
Message Closed
modified 22-Sep-15 15:34pm.
|
|
|
|
|
What made you feel like it was ok to come in here and insult me - twice?
If it's not broken, fix it until it is
|
|
|
|
|
jibalt wrote: Don't quit your day job.
This kind of thing is why most aspiring writers quit. Writing fiction is like learning a musical instrument, it doesn't matter much how good you are now, the main thing is whether or not you stick with it and put in the practice. Keep writing daily and ignore the naysayers, and you're ahead of 90% of the competition.
|
|
|
|
|
Aspiring writers quit because of snarky comments in sewers like the CP lounge? I don't think so.
|
|
|
|
|
Kevin Marois wrote: “Thank you, I will Brother.” he replied, “God Bless”
... should be "Thank you, I will Brother," he replied. "God Bless."
|
|
|
|
|
Message Closed
-- modified 4-Aug-15 11:14am.
|
|
|
|
|
Have you tried turning it off and on again?
Rules for the FOSW ![ ^]
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
Have you tried asking for help in the appropriate forum?
You can lead a developer to CodeProject, but you can't make them think.
The Theory of Gravity was invented for the sole purpose of distracting you from investigating the scientific fact that the Earth sucks.
|
|
|
|
|
Couple of things:
1) Ask in the right place: http://www.codeproject.com/Questions/ask.aspx[^] - this is not for questions as it clearly says at eth top of the page.
2) Don't ask for code, or for a general "help me to create this app" - you need to ask a specific question, and show us that you have tried, what you have tried, and where you are stuck. We don't do homework, and we don't do your job either! 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
First of all, I see you are a new member of Code Project, so welcome. I hope that you come to enjoy your time here, and find it a valuable resource.
Unfortunately, you have chosen to post what could be considered a programming question in the Lounge. This is one of the few areas of CP where programming questions are looked down on. You will get a lot of flippant or sarcastic replies because of this. In future, you should think about what forum you need to post your question in. Saying that, your question is actually a request for someone else to help you write the source - again, this is something that tends to be looked down on here in CP. We do like to see that you have made an effort. We will generally help with specific problems - requests for work are ignored.
I will add that your question betrays a lack of understanding of certain items of web development. In all but the simplest of static pages, you are not just going to be writing HTML - you are going to be using JavaScript, and you will have code running at a remote server - this will handle things like retrieving your tasks, saving them, logging in, validation, and so on. When you write your question, you need to be very careful about the terminology that you use because you can easily end up getting answers to the wrong question, just because we answered the question you asked.
|
|
|
|
|
You must have a copy of that post that you use just for these situations -- I seem to remember reading something exactly like this on other occasions!
Marc
|
|
|
|
|
It's a variation. I really should keep a master copy. It would save a bit of time.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
