Scientia Weaponizes The Future

Exactly, some use optronics to solve the electron computer issue, or dimensional/space tech to fold space and bypass the issue. "Dump the waste into hyperspace" nicely sums it up. Dump all the extra energy sideways of the local 3D slice and do whatever you want with it later, and use molecular circuitry so cableing isnt a problem, especially as the builds become larger and the detail more precise. Combined with better material science and actual quantum mechanics you can get away with pretty much anything and leave it still making (some) sense.
Depending on the temporal mechanics of a universe you could completely bypass it by linking a, I don't remember if it was RAM or a Processor, to a time machine by outputting a cycle of calculations back in time repeatedly until you have the answer In less than a CPU cycle.

I mainly remember this because in a fanfiction the guy failed to make the chip work but it was still useful to obscure precognition, because you may end up paying attention to it adding enough quantum instability to through off most variations of future sight.
It's like Schrödinger's cat you both are and aren't paying attention and making decisions based of it.
I mention that because I can't remember if Taylor is still having issues with precogs in this story (might be time for a reread), but I do remember something along the lines of time travel is theoretically possible but requires so much energy it's not viable to send anybody/thing back
 
Depending on the temporal mechanics of a universe you could completely bypass it by linking a, I don't remember if it was RAM or a Processor, to a time machine by outputting a cycle of calculations back in time repeatedly until you have the answer In less than a CPU cycle.
Other interpretations of temporal mechanics allow you to have the answer in one CPU cycle but only if you do the work to actually calculate (or at least verify) it afterwards. Regardless of the mechanics, each step of the calculation must have been performed in some timeline or other, or else the result is arbitrary data instead of an answer.
 
When you say custom-designed, they can basically give a material any property they want? How? What are the limits?
Respectively:

1) By doing cruel and unusual things to fields in particle accelerators.

2) High but not infinite.

Edit:
For a clearer answer, it's not exactly giving a material any property they want. Instead they're breaking conventional matter and remaking it into their own subatomic particles with tuned properties, and then building more complex custom matter from there. The tech emerged out of their research into how to break the FTL barrier, where they needed to figure out how to make matter with negative mass in order for their drive to work. Once they figured out how to change mass they figured out how to change other things, too, and do chemistry with all sorts of weird (exotic) matter. It mostly takes energy, time, and as many machines working in parallel as possible to crank out substantial amounts of material. Alongside FTL it's probably the best trick the origin civilization ever figured out.
 
Last edited:
I love reading stories that include advanced science/pseudoscience, and I have always wondered how an author decides where to draw the line between reading up on the theory to make the science realistic and just deciding that the science is handwaveium mixed with some proper-sounding grammar.

Personally I don't think it matters much honestly, you can go full space magic if you want, or hard as hell real, the more important thing is consistency.

If you make a rule for your universe, do not change it for the plot, that way leads annoyance and nitpicking readers.

Also important, if you come up with a cool technology for your setting carefully think about the implications towards your world. Example Star Trek and the transporter, it was put the show to save money on landing scenes and half a century later it's a stone around the neck of writers ("why didn't they beam X?"). There is a reason most sci-fi doesn't use it, it really nerfs tension.

I recommend throwing the tech to a bunch of table top gamers and asking them what is the most broken thing they can do with it, you'll soon learn what limitations you need to put on it to prevent your readers crying 'idiot ball' when your characters don't abuse it.
 
When I was younger I absolutely adored hard science fiction, like my dream was to be able to write like all the greats! But I'm kinda dumb, so I stick to funny punny little short stories. Honestly what I do write reads more like bad Terry Pratchett fanfiction then good science. Also funnily enough I can't stand most first person perspective but that's all I can write effectively.
 
Writing Advice: Tense, Person, and Perspective
When I was younger I absolutely adored hard science fiction, like my dream was to be able to write like all the greats! But I'm kinda dumb, so I stick to funny punny little short stories. Honestly what I do write reads more like bad Terry Pratchett fanfiction then good science. Also funnily enough I can't stand most first person perspective but that's all I can write effectively.
I think you might be selling yourself short; you're capable of appreciating hard sci fi, and I think that means you could work your way to writing it with research. Just do it progressively and don't get overambitious at first, or it'll feel like you've run face first into a cliff, and that will definitely make it feel impossible.

Person and tense are an interesting discussion that I have opinions about.

For anyone unfamiliar, person is the perspective a story is being told from, and tense is the temporal relationship between the narrator and events, whether they happened in the past or are happening in the present.

Person has three options:

1st Person: "I threw the ball." First person is great for stories that are tightly focused around a central character. Scientia is in first person for this reason. It's great for that kind of story because first person immediately gets the reader inside the head of the main character. This helps the audience identify with them as quickly and strongly as possible, which is very useful. The downside of first person is that it makes it harder to tell the inner stories of other characters, although there are tricks for doing this. You can have multiple point of view characters that switch between chapters (an advanced technique, it can get confusing in a hurry) or do what I did in Scientia and have interlude chapters in 3rd person. Most of the time though you tell the inner stories of other characters through characterization. Their expressions, the way they react, all that tells a story to the audience. Grammatically this works out to the main character's actions being in 1st person and the actions of everyone else looking the same as they would in 3rd person.

Your mileage may vary, but the general thinking is that 1st person is somewhat easier to manage for a newer writer than 3rd person. Mostly because there's less to keep track of with one main character than several, and because it makes building reader rapport with the main character relatively easy. You're free to get directly in their head in the narration, freeing you to explore their inner commentary and reactions to events, without having to hint at what they're thinking to the audience indirectly. You'll still have to do that for the secondary characters, but for the main character your hand is much freer.

2nd Person: "You threw the ball." I would never use this except for the case of a forum quest where the reader is controlling the main character.

3rd Person: "He threw the ball." Third person is great for when you want a large cast of characters and don't want to be restricted to focusing on any one character exclusively as your lens through which the reader sees the world. The downside is that you have to work harder to convey character's inner lives to the reader. Some people try to cheat this by just stating what characters are thinking in the narrative, but I think it's always clunky and awkward and advise against it.

Whichever you choose, be as consistent as possible. Some would say never change, but arguably techniques like switching POV between chapters and having interlude chapters are, they're just broken up and framed in such a way that the switch isn't quite so jarring as it would be mid-chapter. (Which you should definitely never do.)

Tense technically has three options, but really two:

Past tense: "I threw the ball." Past tense is the gold standard for long form adult fiction. Unless you're absolutely sure you know what you're doing and why, always use past tense.

Present tense: "I throw the ball." You sometimes see present tense in young adult fiction, and almost never in adult fiction. There's nothing wrong with it per se, it's just not what most of your readers will be expecting and some percentage of them will find it rather jarring. I believe it's best avoided for that reason, but this opinion is not without controversy.

Future tense: "I will throw the ball." Included for completeness only. Only lunatics write whole stories in future tense. If you encounter such a writer in the wild, back away slowly and make no sudden movements. They may be rabid.

There's also something else worth mentioning, which is the perspective of the narration. There are two options here.

Omniscient perspective: The narrator is speaking from the perspective of knowing everything that's going on. There's two general approaches to this. The narrator might be taking the perspective of a god or a greek chorus commenting on events. "Little did John know that his day would soon take a turn for the worse." That's the version you usually see in 3rd person omniscient. The other approach is to have the narration coming from the perspective of a character retelling events with the benefit of hindsight and future knowledge. "Little did I know then that my day would soon take a turn for the worse." That's the more common approach in 1st person omniscient.

Omniscient perspective is very much out of fashion. It used to be more common, and it can work in the right kind of story, but I would caution against using it unless you're very sure you need it for a particular purpose. Most of all be consistent. Authors sometimes randomly switch into omniscient perspective for a bit and that's jarring. Anything you can get across in omniscient perspective that you need to get across you can get across in limited perspective, you just have to sometimes be a little clever about it. Give it some thought and you'll come up with a way, even if you have to massage events to convey whatever clue you want to your reader. You're the god of the universe, you can do that.

Limited perspective: The narrator only knows what the main character in a scene knows. In 1st person this is obviously limited to whatever the perspective character sees/hears/knows/etc. They won't narrate someone sneaking up behind them if they don't notice them, they'll narrate the sudden surprising pain of the knife in their back, or whatever. In 3rd person you'll still have a 'main character' of sorts, or possibly a group of them, that the narration is proceeding from the perspective of. This is sometimes described as an 'over the shoulder' view.

Limited perspective is the modern standard. It's useful because it preserves tension and mystery that would be lost with an omniscient narrator constantly spilling the beans. Tension is a virtual necessity in any kind of engaging story, even light and fluffy stuff, and mystery is a pretty common sort of plot, even if it's as a secondary element. (Mystery doesn't have to be like a murder mystery, it just means that the main character(s) don't know everything that's going on and find out over the course of the story. The two big mysteries that Scientia wrestles with are 'What's up with my power?' and 'How did I wind up in Worm?'. I gradually inserted clues to those over the course of most of the story, and as secondary elements they've now been resolved in time for us to head into the climax and denouement of the primary story element, which is action/adventure.)

In summary, and this is my personal (but reasonably informed) opinion, most people writing fiction should choose between 1st person limited past tense, or 3rd person limited past tense. The major determining factor is whether you can tell the story through one character's eyes or if you'll have to have several throughout the whole story. Other options are possible but should be considered advanced techniques to be used when you're very sure you know what you're doing and why.
 
Last edited:
This sounds like a challenge.
I knew someone would take it that way. XD

There are people who have done it and had it sort of work. If someone made me do it, I might write some sort of short vignette of a prophet speaking prophecy or something of that nature. Maybe something from the perspective of a time traveler. But it really doesn't work for standard storytelling. I think it would get annoying to read in a hurry.
 
Last edited:
2nd Person: "You threw the ball." I would never use this except for the case of a forum quest where the reader is controlling the main character.

It arguably has literary merit in Interactive Fiction games. Consider this case, taken from Fallen London, where the player engages their rival in a battle of words:

W--- with the m---- and your d----!
You spit foul recriminations and vicious calumny. Ladies faint dead away and gentlemen stagger under the barrage. Your target runs, weeping, with her hands over her ears. You follow her! Your tirade continues in the street, where hansoms careen hastily off and urchins fall from rooftops. You pick up your victim's dropped letters and wave them as a final salute. You are spent.

I think it works. More to the point, I don't think this scene would be nearly as funny in a more conventional tense or perspective (not without adding substantially to its length, at any rate).
 
Last edited:
It arguably has literary merit in Interactive Fiction games. Consider this case, taken from Fallen London, where the player engages their rival in a battle of words:




I think it works. More to the point, I don't think this scene would be nearly as funny in a more conventional tense or perspective (not without adding substantially to its length, at any rate).
Yes, that's essentially the same use as a forum quest. A GM in a tabletop game could use it the same way.
 
2nd Person: "You threw the ball." I would never use this except for the case of a forum quest where the reader is controlling the main character.
It was used in Harrow the Ninth, for the sake of a pretty fantastic reveal that made it worthwhile. But yeah, this one's "don't use without a reason".
 
It was used in Harrow the Ninth, for the sake of a pretty fantastic reveal that made it worthwhile. But yeah, this one's "don't use without a reason".
Interesting, I didn't know anyone had done a long form novel in 2nd recently. Thanks.

Just goes to show that there are exceptions to every rule.
 
Last edited:
Interesting, I didn't know anyone had done a long form novel in 2nd recently. Thanks.

Just goes to show that there are exceptions to every rule.
Charles Stross wrote two excellent near-future SF mystery novels in second-person perspective, Halting State and Rule 34. For both of them, I think he was deliberately evoking the feel of old text adventure games, and there's a strong implication that the second novel is actually being narrated by a rampant AI. Also, I think maybe Penn Jillette wrote a second-person perspective novel about a sock-monkey, but I read it something on the order of 20 years ago so my recollection may not be accurate.
 
Charles Stross wrote two excellent near-future SF mystery novels in second-person perspective, Halting State and Rule 34. For both of them, I think he was deliberately evoking the feel of old text adventure games, and there's a strong implication that the second novel is actually being narrated by a rampant AI. Also, I think maybe Penn Jillette wrote a second-person perspective novel about a sock-monkey, but I read it something on the order of 20 years ago so my recollection may not be accurate.
That's clever, to write a book evoking the feel of second person text adventure games. A good reason to do it.

Nothing about Penn Jillette would surprise me at this point, the guy does all sorts of stuff.
 
I'm an IF author. I like Stross' writing. From what I saw of Stross' attempt, however, it rather fails to capture the voice of parser games, which are surprisingly technical in how you shape space, which details you choose mention and how, cadence, et cetera.
Of course, I've only ever read excerpts; YMMV.

Where am I going with this? Right; it's that certain conventions of any given style or form will be nonobvious. Another example of that is script-writing, which offers a similar plethora of textures and techniques that you don't really get in regular literary prose.
 
Last edited:
To be fair, the great thing about creative writing is that you can try out different things. There's a famous Swedish short story called "Att döda ett barn", or "To Kill a Child", where a present tense narrator is constantly shifting focus between a child sent to borrow sugar from a neighbour and a driver on the way to work, and it constantly repeats a line telling you that "he doesn't know he's about to kill a child" when narrating about the driver, and that the family doesn't know this is the last time they'll see the child alive when talking about the family.

This is called planting, and it basically means the reader knows exactly what's about to happen from the start, but the anticipation and dread still builds. This wouldn't work for a novel, but short stories can be pretty unorthodox without outstaying their welcome. For the narration to be omniscient about future matters, the scope of the story needs to be very limited. Simply using the future tense to tell a story is definitely possible, but it would probably just be unpleasant to the reader if used as anything other than an interlude to show a prophecy, a plan, or a hope or fear for the future.
 
TLDR of it, is if you want a crazy hard writing challenge, write an entire story in 2nd Person in the future tense.

If you manage to make something good out of it, you're good enough to go pro. :evil:
It's one of those 'because it's there' challenges, I think. I think effort would be better spent doing something else, like writing a saleable novel, but if someone gets excited about it then they should write what will get them writing.
 
It's one of those 'because it's there' challenges, I think. I think effort would be better spent doing something else, like writing a saleable novel, but if someone gets excited about it then they should write what will get them writing.
You never know, the author of Love Crafted (on Royal Road) started the story as a self challenge exercise in the 2nd person IIRC, and that story turned out pretty great.
 
To be fair, the great thing about creative writing is that you can try out different things. There's a famous Swedish short story called "Att döda ett barn", or "To Kill a Child", where a present tense narrator is constantly shifting focus between a child sent to borrow sugar from a neighbour and a driver on the way to work, and it constantly repeats a line telling you that "he doesn't know he's about to kill a child" when narrating about the driver, and that the family doesn't know this is the last time they'll see the child alive when talking about the family.

This is called planting, and it basically means the reader knows exactly what's about to happen from the start, but the anticipation and dread still builds. This wouldn't work for a novel, but short stories can be pretty unorthodox without outstaying their welcome. For the narration to be omniscient about future matters, the scope of the story needs to be very limited. Simply using the future tense to tell a story is definitely possible, but it would probably just be unpleasant to the reader if used as anything other than an interlude to show a prophecy, a plan, or a hope or fear for the future.
It's not too uncommon for a novel to have the narrator drop in prophetic statements (or hindsightful statements, from their theoretical perspective narrating something that already happened). Sometimes misleading or even outright dishonest, but not always. Of course that's very different from the matter of writing in an unusual tense.
 
Writing Advice: Beta Readers, Beta Reading, and Editing
This isn't in response to a question, but it's an important topic.

Editing is really important. As an author you probably want people to read and enjoy your work. Some people will still read messy, unedited work, but far more will read the same story with clean prose that doesn't have any SPAG (spelling, punctuation, and grammar) mistakes or awkwardly phrased sentences and all the rest of the basic workmanlike stuff that's expected of good quality work.

Finding and correcting all that stuff is called line editing. (Or proofreading or copyediting, if you prefer. Some people draw distinctions, but they're all pretty close in concept.) Line editing involves reading through line by line and finding all the stuff that needs to be fixed on that small scale. Every story should have a line editing pass, because no writer on Earth writes utterly pristine prose in long form on the first pass. I pride myself on writing really clean prose and even I have to make a fair number of corrections per chapter. These days google docs (which is fabulous for writing from multiple machines and sharing work with editors with the comment/suggestion feature) catches much of the obviously ungrammatical stuff on its own, but I still have to go through and check dialogue punctuation, look for awkward sentences that need to be broken up or rephrased, find the occasional missing or incorrect word, catch a random tense change, find continuity errors (like someone sitting down and then sitting down again a paragraph later without standing up in between), sort out places where I edited part of a sentence but didn't correct the rest of it to match, that sort of thing.

There are also two other more advanced kinds of editing, often called structural and developmental editing. These are more into the territory of serious professional editors with lots of experience in how long form stories work. These are about addressing the work mostly on a larger scale than lines. This scene/character/subplot isn't working and needs to be changed/cut, that sort of thing. Questions like 'How does this serve the story as a whole?' come up a lot. Professionally edited novels often see cuts of at least 10% in length when they go through professional editing, and this is the kind of editing that results in most of that slimming. Authors often include stuff that just doesn't work and the story can be stronger without it. (Imagine the Star Wars prequel movies if Jar Jar was cut and the romance subplot rewritten.)

So, on to the general mechanics of editing. Discussing the common sorts of errors is beyond the scope of this advice, but I can give some general insight and advice that will hopefully be useful.

It's a fundamental truth of the human brain that writers have a harder time seeing our own mistakes. We just unconsciously insert what we meant to write rather than what we did write, because we're familiar with the writing. A competent outsider will always be more likely to spot an error than the author themselves. Although the author should always make an editing pass anyway before handing it off, if they do have an editor, or at least do the best they can if they don't have anyone.

There are some tricks that work to compensate for this author blindness phenomenon somewhat. If you can wait a significant period of time (at least overnight, but preferably a week or even a month or more, the longer the better) between writing something and reading it again with a critical eye, your familiarity with what you wrote will lesson thanks to fading memory. This is good because you'll be more likely to see what's actually there than what should be there. There are famous authors who swear by leaving a manuscript in a drawer for a few months before going back to it. (And then giving it to a professional editor after they make their editing pass, of course.)

Another trick is to read the material you want to proofread backwards. Read the last sentence, then the second to last sentence, then the third to last sentence, etc. Deliberately breaking the familiar flow of the story this way helps to make mistakes stand out.

Let's talk about how to judge the quality of volunteer editors/beta readers.

If you write stuff on the internet for free, you'll probably have to recruit some free beta readers/editors who are volunteers. A good way to do this is to ask in an author's note for volunteers, and if you spot readers who are writers themselves or have really well-written comments you can ask them directly. Perhaps 1 in 4 volunteers will work out if you're lucky, so it could take some work. But it's worthwhile, because a good beta-reader/editor will spot mistakes you don't and they'll be able to tell you what just isn't working and needs to be changed before it goes live.

Here's a rough field guide to the different kinds of volunteer beta readers/editors you are likely to encounter:

1) The Disappearing Act:
Volunteer: "Sure, I'll help!"
Author: "Great, here's a link to the chapter."
*crickets*
Verdict: People get busy and have lives. They want to do stuff but it falls off in favor of other things. Just move on.

2) The Ideas Guy:
Volunteer: "Sure, I'll help!"
Author: "Great, here's a link to the chapter."
Volunteer: "Hey, I read some of this, and I don't have any edits but I've got this great idea for a plot you should do..."
Verdict: Fire into the sun. This sort of person isn't there to help you make your story better, what they want is for you to do all the work of writing their story.

3) The Well Meaning But Insubstantial:
Volunteer: "Sure, I'll help!"
Author: "Great, here's a link to the chapter."
Volunteer: "Thanks, I liked it a lot."
Verdict: This sort of person mostly just wants to read chapters early, or doesn't know how to provide useful feedback. If you're really desperate you could try training them, but it's probably not worthwhile.

4) The Inadequate But Useful In So Far As It Goes:
Volunteer: "Sure, I'll help!"
Author: "Great, here's a link to the chapter."
Volunteer: "Thanks, I liked it a lot except for that second scene, it seems a little abrupt?"
Verdict: This sort of person wants to help but doesn't really know how, or doesn't appreciate the sort of detail that an author really needs to work with in order to get started making improvements. You could try training them if you don't have any better options, but it'll be time consuming and it's far from a sure thing you'll get them to a place where they're helpful to you.

5) The Actually Starting To Do Editing:
Volunteer: "Sure, I'll help!"
Author: "Great, here's a link to the chapter."
Volunteer: "Here, I marked up a bunch of spelling/grammar errors and places where I was confused for you to have a look at."
Verdict: This sort of person is a source of valuable, practical error spotting and feedback. It's not spectacular, professional editor level comprehensive insight yet, but it's easy to use to make the story better than it would be without the extra look. Worth keeping. They might naturally get even better over time, especially with specific questions that steer them to look at things you want a reader's perspective on.

6) The Solid Gold:
Volunteer: "Sure, I'll help!"
Author: "Great, here's a link to the chapter."
Volunteer: "Here, I marked up a bunch of spelling/grammar errors and places where I was confused for you. I also made a bunch of suggestions for improvements in places where the phrasing was awkward, go with them if you like them better. I think there's one continuity error because of stuff that happened three chapters ago, I left a comment about it, and I think the second scene might be problematic as it is currently. There's a comment about what's working and what's not working, and some suggestions on ways you might fix it or move the important stuff into the next scene instead. Also, I did some research on the explosion in the fourth scene and I think you should scale back the amount of C4 the protagonist used to avoid blowing everyone up. It's all in a comment. Overall I enjoyed it, the action in scene 4 was a highlight and the character development with X and Y burying the hatchet in scene one was enjoyable. I especially liked the characterization you did there. The second half of scene 3 was a bit slow and could probably stand to be tightened up."
Verdict: This sort of person is passionate about the craft of writing. They know writing, they know editing, and they know how to help a writer improve both the story and themselves as a writer. They might be at a professional editor's level of knowledge, or verging on the edge of it. They may or may not have any formal training, and they may or may not have written extensively themselves, but they've put the work in to learn at least substantial portions of the art. Learn what they're good at and take advantage of that expertise. Treasure them and their input.

So as you can see, some people take 'beta reading' to mean reading the chapter ahead of time without doing much, or they just vanish into the ether. Those aren't terribly useful, even if they mean well. Someone who gives some feedback on what works (and even better, what doesn't) is better than nothing, but the really valuable beta reader/editor is someone who actively helps you make each chapter better, whatever the level of knowledge about the craft of writing they have.

It can sometimes help to communicate specific concerns with your beta reader/editor about particular things you're unsure about, 'Does the characterization here come across as feeling right?', 'Is this action scene exciting?', 'Is this joke funny?', that sort of thing. A big part of what they're there for is to give you an outside perspective because you're too close to the story to know how it looks to a reader.

When you find a good volunteer, hold on to them, thank them frequently, and credit them for their work. They're really valuable, all the more so if they're going to all the trouble to help for free.

For those of you who beta read/edit other works, hopefully this gives you some pointers in how you can be of the most help. A good technical grounding in writing mechanics is a big help, along with concrete line editing. But you're also the author's outside eyes; they can't see the story like the reader can, so they need your opinion on what you enjoyed and where you were bored, what seems to work and what doesn't, what you're excited to see next, all of that is valuable, and the more detailed and specific you can be the better.
 
Last edited:
Back
Top