I Feel Guilty Wanting People To Comment.I Feel Like If My Work Was Good Enough, They Would :(

New Fic Announcement!

I present y'all some analogical fluff in these trying times with wolf shifter virgil & unaware human Logan

https://archiveofourown.org/works/47343466/chapters/119295535

New Fic Announcement!

I finished some family fluff with Logan and Virgil having fun together, set in the Damocle's Universe:

Repeat after me:

The first draft just needs to exist

The second draft needs to be functional

The third draft needs to be effective

The first draft just needs to exist

The second draft needs to be functional

The third draft needs to be effective

The first draft just needs to exist

The second draft needs to be functional

The third draft needs to be effective

Remember, the second and third can't happen if you don't have something to work with. Your first draft will always be shit compared to your third, but at least it exists. The worst first draft is an unfinished one. The best first draft is a just completed one.

You read books/stories not in their first draft form-- only in their finished form (third, fourth, sometimes fifteenth draft). So stop comparing your first draft with a final one.

So, just write--you can make it better later. Perfectionism is the greatest weight a creator can carry.

Years and years ago, I read a book on cryptography that I picked up because it looked interesting--and it was!

But there was a side anecdote in there that stayed with me for more general purposes.

The author was describing a cryptography class that they had taken back in college where the professor was demonstrating the process of "reversibility", which is a principle that most codes depend on. Specifically, it should be easy to encode, and very hard to decode without the key--it is hard to reverse the process.

So he had an example code that he used for his class to demonstrate this, a variation on the Book Code, where the encoded text would be a series of phone numbers.

The key to the code was that phone books are sorted alphabetically, so you could encode the text easily--picking phone numbers from the appropriate alphabetical sections to use ahead of time would be easy. But since phone books were sorted alphabetically, not numerically, it would be nearly impossible to reverse the code without exhaustively searching the phone book for each string of numbers and seeing what name it was tied to.

Nowadays, defeating this would be child's play, given computerized databases, but back in the 80s and 90s, this would have been a good code... at least, until one of the students raised their hand and asked, "Why not just call the phone numbers and ask who lives there?"

The professor apparently was dumbfounded.

He had never considered that question. As a result, his cipher, which seemed to be nearly unbreakable to him, had such an obvious flaw, because he was the sort of person who could never coldcall someone to ask that sort of thing!

In the crypto book, the author went on to use this story as an example of why security systems should not be tested by the designer (because of course the security system is ready for everything they thought of, by definition), but for me, as a writer, it stuck with me for a different reason.

It's worth talking out your story plot with other people just to see if there's a "Why not just call the phone numbers?" obvious plot hole that you've missed, because of your singular perspective as a person. Especially if you're writing the sort of plot where you have people trying to outsmart each other.

Reblog if you write fic and people can inbox you random-ass questions about your stories, itemized number lists be damned.

newbie fic authors, shooting themselves in the foot: This fic is bad haha I suck at writing lol I am being mean to myself in the hopes that you will be nice to me but actually am dissuading anyone from even clicking on my fic because all I have done to advertise it is tell you why you shouldn't read it

me: I am King Big Dick of Fanfic Mountain and I have arrived in your fandom with the Express Intention of writing my Very Favorite Fics, which I will generously allow you to read. You're welcome.

How to write a good AO3 summary so people will actually want to read your fic

Summarize your story.  Don’t be vague or coy.  No hiding the pickle.  There are so many fics and so little time.  More people will skip over your fic if they don’t know what it’s about than will be turned away because it’s not about something they’re interested in.  Tell the reader what happens!

A snippet is not a summary.  People like to use lines of dialogue or excerpts to grab the reader’s attention.  Very rarely do these snippets provide enough information to summarize the story.  If you want to showcase a clever line of dialogue or the tone of the fic, include a line, but after the actual summary.

Make sure the summary is clear and written well.  If it is messy and full of errors, people will assume the same of the fic.

Focus the summary on the characters and what happens to them or how they feel about each other.  Fanfic readers come to see the characters they love do things they didn’t get to see in the source material.  Let the audience know what the characters are doing and feeling.

Don’t forget to tell the reader what makes your story unique.  Lots of fics are successful almost entirely because they follow a much-loved trope, so talk about that too (definitely in the tags at the very least), but when staring at the hundredth fic about one character pining for the other and deciding whether its worth it to read another, the reader is going to look for extra details that spike their interest.

Hint at the tone of your fic in the summary.  If it’s light, give the summary a chatty tone.  If it’s angst, make it hurt.  If it’s plot-driven, go matter-of-fact.  If it’s a character piece, meditative and dreamy.  

Don’t contradict yourself.  Don’t write a summary and then immediately undercut your description by trying to soften the blow.  Just get the summary right from the get-go rather than mischaracterizing the work and then backpedaling with “trust me, not as angsty as it sounds” or “this is actually total fluff.  And if it really is as angsty/dark as it sounds, let it be angsty with confidence.  There are readers out there who will love your fic for what it is and will be turned off by a waffling summary.

Don’t reference yourself.   The fic is the star of the summary, not your ego.  Don’t explain why you wrote it (unless you’re listing a short prompt).  And definitely don’t make any self-referential jokes, give your opinions on the characters, use the summary for foreshadowing, or compare it to other fics.  

The summary is not the place for self deprecating humor, false modesty or insecurity.  Don’t say it’s your first fic.  Don’t apologize.  Don’t say that English isn’t your first language.  If you must, do this in the author’s notes, but better to not do it at all.  The worst you might get if you don’t warn for these things is the suggestion you get a beta or some concrit.  Most people will just skip your work entirely.

One paragraph only!  Readers are skimming a list of summaries.  They probably won’t stop to read all of yours.  See points 10-13 for more on this.

Don’t use the summary for warnings.  Warnings are for tags and author’s notes.  Make sure you warn for all possible triggers, but these are reasons for people not to read the fic, not reasons to read it (if they are reasons to read it, then phrase them as part of the summary not as warnings).  Warnings can easily overwhelm a summary to the point that it becomes about why the reader should probably just not read it rather than an enticement to read.

Remember the reader can also see your tags and that tags help the reader find the right fics.  Put any tropes that might be selling points in the tags and leave the summary for information that is unique to the fic/gets at the backbone of the fic.

Remember you have the author’s notes.  This is great place to tell us why you wrote the story, give a long prompt word-for-word, thank your betas, give more detailed warnings, reference inspirations, and gab on about yourself.

The summary is not the place for worldbuilding.  Don’t explain the intricacies of your AU in the summary.  If it’s a very strange world, you get one sentence max to describe that world.  Spend the rest of the summary on the substantive character arcs.  If the reader can’t understand your AU from the text of the fic itself, you’re doing it wrong.

It doesn’t hurt to sell yourself.  Phrase things in a pithy, clever way, let the readers know you’re going to deliver on their favorite trope, and keep the tone confident.  This is the inside flap of your hardback.  This is the summary on amazon.  Think about what would make you buy.  

Do not write “I suck at writing summaries” in your summary.  If you can’t trust yourself to write a summary, why should the reader trust you to write a good story?

that post that’s like, fandom’s obsession with viewing characters as only relatable or shippable or defendable has ruined media literacy in being able to view characters through the lens of themes or narrative theory. character analysis one of my favourite forms of analysis but not at the detriment of being able to understand when a character represents something larger thematically in a story than what they would be if they were just a guy from your high school

Hi, same anon here, wanted to thank you for the reply and also tell you that your writing is amazing, i enjoyed the story a lot it's one of my favorite anxceit stories I've ever read, I'm not sure if you already posted this story on ao3 or not but I'm pretty sure people on ao3 would appreciate it a lot :)

Aw I'm flattered that you like it! It's on ao3 but I still haven't added the last chapter (I should probably get to that oops). There's a link on the masterpost too if you want to show it some love on ao3 (no pressure, just a side note) <3

Map for Damocles’ Gambit

The whole green land belongs to Alyria (Askanian is only shown as independant cause they still have their king as a respentive figure & some different laws than the rest of the empire)

Note: I made this map before I established that Iudin is north of Alyria - so on this map north is to the right and south to the left.