WonderCon 2018 was amazing! So much more relaxed than Comic-Con.

I’ll do a summary post about the Con later this week, but I wanted to get my notes from Day One up first thing :)

Note: Some of the panelists’ names are probably misspelled, because I couldn’t always get close enough to see their placards :/

A story is a story: writing in multimedia

• sam sykes: bring down the heavens series; also munchkins series
• Sarah kuhn: heroine complex series; also comics
• Judd winick: artist and writer for dc comics and indies
• Judy ann neeb: librarian and moderator
• What was your first writing medium?
  • Judd: comic strips; was meat and potatoes work, you write and draw and ink and letter everything yourself, then send it out
  • Sarah: zines; at the time, heard you could write everyday and get paid for it by being a journalist; so middle school started their own zine, photocopies printed out and gossip about cheating on math tests, etc
  • Sam: devoured every dragonlance novel ever, and then all the dragons disappeared, so what’s the point, might as well write his own thing now, started with prose because art was hard, went right to novels, because that’s what he’d read, sold first novel at 25, but had been working on it since 14
• Weird how market has shifted, short fiction is basically dead, can barely sell it, let alone make a living at it, unless you do nothing but anthologies, or maybe you get known as a novelist first, which is backwards, thirst for short fiction isn’t dead, though, just look at subreddits for people posting and consuming it by the ton, we’re just looking for the next way to do it
• Short fiction used to be the minor leagues for writers, eventually would get asked to do a novel, but nowadays path seems to be through self-publishing more than short fiction
• To be a creator today, you almost have to master multiple media, unless you can just knock one of them out of the park, to keep up with everyone else, need to be in many places at the same time
• Sarah’s approach to comics: voltron-ing skills?
• Judd: Everything other than one-room-one-person work (which is rarer now) means working with a team, so have to work on your social skills, interact with other people and compromise with them, in larger teams, bottom-line is still storytelling within the tiny garden you’re given
• Sarah: whenever starting a new kind of writing, still feels like an imposter, owes her current career to short fiction, wrote geek-girl rom-com for her friends, serialized it online, did a pdf zine, got a bit of a following because wasn’t that many geek-girl protags, that series helped her get an agent when she had a novel ready; was approached to write comics, someone asked her to, she said yes but i have no idea how to do it, she did a lot of research before diving in, reading and interviewing and going through samples, before realized it is telling a good story at its base, same basic skills, though with different scaffolding on top
• Judd: not enough credit given to editors who find people say “do you want to do this?” and barrel through objections from the writer about not knowing how to do it
• Sam: as the mediums change, you start relying on more and more people, novels is just him and an editor, comics is him and artist and editor and letterer, etc, what it comes down to is the ability to trust other people, you’ve got this idea and you’re trying to get it out there, and trusting other people in that process is hard, comics is littered with the carcasses of writers who did not understand that trust of the artist that’s needed
• Judd: best advice for writing comics from bob shreck the editor and founder of oni press: write the script like it’s a letter to your artist, like you’re talking to a person, and that’s how you can make things a partnership
• Worth mentioning that artists understand geometry and positioning better than you do
• Has there ever been a point in your writing where you’ve wanted to change the format? From comic to novel, or novel to script, etc
  • Judd: never been able to switch gears; not that the option is always there, don’t sit around saying “i think this would be better as a major motion picture, lemme make a call”; people have asked him to do prose, but when he starts thinking of a story, by the point he’s excited about it, he wants to draw it, that’s what he enjoys doing as an artist
  • Sarah: never wanted to switch in the middle, gets hooked into whatever the right media is for the story, and sticks with it; tried to make her heroine series very visual, since they’re inspired by comics
  • Sam: one of the marks of being a professional is putting your head down and barreling through, can’t chase every thought in your head, unless you’re pat rothfuss (and if you tell him i said that, i’ll tell him you’re lying, and he’ll believe me); your idea of perfect keeps changing, so no use in chasing that perfect, best to do many projects at the same time, not all of them have to be finished at the same time, if you have a novel, nothing can stop you from tweaking it a little and making it a comic, but if you want to do it as a living, you have to barrel through and finish it, which means you have to choose
• Judd: advice he gives to kids about writing: know your ending, if you’re going to do a novel, do it, finish it, get a draft, and then you can edit it and make it better; writing is the worst, he likes editing, when he can fix it
• Sam: a little like constipation, sometimes you just gotta sit down and force it out
• Judd: greatest job in the world, we get to make shit up and people pay us money, i’m 48 and i draw and half-watch television, like when i was ten
• Sarah: often feels the script for comics ends up being a conversation back and forth between writer and artist(s), her first comic was smaller team, used to tell the colorist “more sparkles!”, felt like her own little clubhouse, initial scripts for clueless series were more detailed, since had a different artist, once they started getting art, got to more a shorthand with her

Spotlight on VE Schwab

• Written 15 novels in 8 years
• No trunk novels, doesn’t start novel until she knows she has enough for the novel to come to fruition
• Longest time, had just an image for darker shade of magic: wounded man falling through a wall and hitting a girl dressed as a boy
  • Six months later, hit on the idea of doing an homage to harry potter, a multiple worlds story
  • What if the young man isn’t walking through a wall, is walking between worlds?
  • That shot became the crystalizing ingredient needed for the book to come together
• Always working actively on one thing and letting 3 or 4 others simmer
• Leans towards fantasy, because grew up wanting the world to be stranger than it is; Wanted the cracks in the sidewalk to lead to other world; as a writer, wants to seed your world with doubt, wants you to look for the stranger things in the world
• Was 11 when harry potter came out, and started reading the books; didn’t love reading at the time, mother’s friend was in a bookstore in socal and called her mom “hey, there’s someone here doing a signing, her line’s not long, it looks like something your daughter would enjoy”… which is why she has a signed copy of the sorcerer’s stone; potter was a hook for her, showed her you could create a story that would make a person forget they’re reading a story
• “What drives the part of your writing where you describe clothes so well?”
  • Really, really loves coats
  • Watching pushing daisies, realized the guy has a really wonderful black trenchcoat
  • Never been very feminine, not a dresses person, but finds coats can be very cool and sexy and not strictly one gender or another
  • Uses fashion because it’s a very good shorthand for a character, lets you visualize the character very easily
  • Kell’s coat is a nod to the room of requirement
  • Kell’s coat, nella’s knives: ways for you to see character easily
• Always been a cinematic writer, resisted writing novels for a long time, wrote short stories and poems and everything else, realized she was afraid of failing to write a novel, so sat down and made herself do it
• Has to see each scene in her head before she can write it; like creating a movie in her head and then translating it into a book
• Loves tv and comics and film, those are her recharge
• Getting to write her first comic now, and that’s so cool because her illustrator can directly translate everything she wants to see
• Nothing better as a writer than to see a lot of fan art and it all looks the same; means you were able to get it across well
• At any given time, have up to 6 projects in development; currently has 3, film makes publishing look very very fast
• “Where does your affection for redheads come from?”
  • Not a natural redhead, is a very light blonde, but never felt like a blonde on the inside
  • Her father is a weasley redhead, and always got teased for it, never felt good about it
• Her male characters are always hufflepuff, and her female characters are slytherin
• Wants to see more ambitious women and emotive men
• “Books not about love, but about entanglements”
  • Loves romance, but so often in fiction, romance supersedes every other kind of relationship
  • And it’s the least interesting relationship, so often these cool dynamics take second fiddle; wants to see more sibling rivalries, more frenemies, etc
  • Loves a long con, where they start out adversaries in book one, but by book three they become involved, because the relationship is built on something
  • Likes room for progress and intensity
  • Really likes familial relationships, thinks rhy and alucard are the core relationship for the darker shade of magic books
• “So how do you feel about ’shipping for your characters?”
  • Sorry, been rewriting a book from scratch for two months, not as articulate as normal, just finished yesterday
  • Fine with shipping, weirded out about it
  • As author brings 50% to the book, reader brings the rest
  • Tries to do nothing to dictate the reader’s relationship to the book and the characters, doesn’t want to control the other side of things
  • Side note: if you have a problem with a female character, especially a strong one, ask yourself if you would be as bothered by them if they were male
• “Interest in monstrosity and monsters?”
  • Grad degree is in medieval depictions of monsters and monstrosity
  • Not interested in monsters so much as outsiders
  • Monstrosity is an easy way to talk about people that don’t belong, to otherness
  • When she does have something that is clearly monstrous, she tries to look at its origins, and explore that
• “Why london for shades of magic?”
  • Two reasons: one, because she wanted to play against the assumptions we have as readers for what kind of story we’re getting in london
  • And two: multiple worlds, all based on the same geography, was thinking how fun would it be if you took a well-known city and take it down to studs, rebuilt it from the ground up with just the geography there, but to do that, needed something a broad audience would be able to imagine with little effort, and london fits the bill: city, with the thames running through it, and bridges, etc
• “Really open with struggles with anxiety, how does that impact writing process?”
  • In savage song, main characters are different aspects of her anxiety: one lashes out, the other shuts down and internalizes everything
  • Didn’t set out to be open about anxiety, set out to be open about publishing
  • When she started, no one was talking about the industry online in an open and honest way
  • It’s very isolating, and you feel like you’re the only one going through it, when really every author feels that way
  • At conferences, she heard other authors griping about it, but then saying they needed to keep the glamour of the job alive, and so shouldn’t talk about it openly
  • She decided: well, i’m going to talk about it, and maybe it’ll help other people
  • Over time, she just became honest about all of it, the publishing, the anxiety, the depression, coming out, all of it
  • Found the most incredible thing: readers started celebrating with her, showing up at events saying “i’m proud of you”
  • Not calculated, not planned, comes from an authentic place
  • 15th book, rewritten in two months, it’s still a struggle, the struggle changes but doesn’t go away
• If you’re writing, even if you’re not published yet, you’re not “trying to write” you’re a writer, we’re all in this tribe together
• “What’s a question you hate getting?”
  • Used to hate “where ideas come from?” Because each book is so different
  • Aren’t any questions she really hates anymore
  • Heard each question enough, tries to answer them in ways that are not just honest but also helpful for others
  • Does get tired of hearing people ask about when the third archive book is coming out, because she knows it hasn’t come out yet, and is very very aware of where it is, it’s a sensitive topic for her
• “Why comics for the steelheart series?”
  • Had this idea for a story, about the king of red london as a prince, with pirates and bad magic, etc, but is working on three more books for the next arc in the shades of magic series already, so thought didn’t want to write it as a book, wanted to do something else
  • Was talking with titan, her uk publisher, and they do comics, asked her if she wanted to do a comic set in the shades of magic world, and she thought: this is perfect
  • So: first four issues are coming out this fall!
• “Also have a middle grade book, and vengeful, the next book in the vicious series”
  • City of ghosts is a weird one, set in edinburgh, scotland, which is where she lives part-time, one of the great things about britain is that everyone has a ghost story, and they’re very blasé about ghosts
  • Middle grade book, but it’s written to 12 year old her, so that’s how she feels like it
  • Girl almost drowns, ghost boy pulls her out, and when she comes back, she pulls him part of the way back as well; her parents pick up a tv series called the inspectors that has them going from town to town doing shows about local ghosts
  • Vengeful: five years have passed since vicious was published, and it’s been five years in that world, as well
  • Has five new female protagonists, and it’s about how women take and hold power in that world
  • So dark, so violent, impressed her how violent it got
  • Comes out in september
• Rapid fire questions:
  • “Live anywhere?”: edinburgh, scotland, just bought a place there, only place she felt like home
  • “Character in other world?”: delilah bard would fit in game of thrones perfectly
  • Favorite villain didn’t write? The Darkling
  • Favorite monster? Voldemort
  • If you had magic, what would you do with it? Definitely rule white london; white london is for the takers, with enough magic, could sit on that throne for a while
• How to switch between middle grade and adult?
  • Only difference is the version of herself she’s writing towards
  • Middle grade: 12 yr old me
  • YA: 17 yr old me
  • Adult: current age
  • Middle grade is beautiful, because you can explore so dark themes, children as so good at reading things that would disturb adults more
  • Tries not to dial anything down, just thinks of terms of writing to herself
• Will the next trilogy be cliffhangers?
  • Doesn’t know
  • Firm believer that the first book should stand alone
  • Apologized for the cliffhanger at the end of book two, but:
  • Second book is a little harder
  • Gathering of shadows was her first cliffhanger, so she went all out for it
  • Should be able to stand a little more on their own, because they will each have their own protagonist, but will build on each other
• Tools that help you write from vast material?
  • Plot is her weakness, plot is not natural for her, so she works on it till it becomes her strength
  • Plot is the skeleton, gotta have it strong to support everything else
  • Marks out five plot points, when she gets to one, she bisects it: what happens halfway between one and two? Etc
  • Had to do a rewrite because spent so much time on makeup for a very badly skeleton’d corpse

Publishing your first comic book

• Ryland grant does stand up during the technical difficulties
• Was supposed to have visual aids, but they’re broken
• Rylend: working screenwriter for years in LA, just recently decided to dive into comics, first book aberrant comes out in june
• Haven’t made comics yet, and you want to? That’s ridiculous, do it
• Never been a better time to get into comics
• Used to have to troll artists alley to get people to draw your book
• Has artists in brazil, in hungary, letterer is in the uk
• Can find everyone with the click of a mouse
• Get off your butts, and do it
• David pepose: interned at dc, first comic spencer & locke (what if calvin and hobbes grew up in sin city) come out last summer, has been pitching everywhere
• Karla nappi: tv writer and script editor, first comic book duplicant will be released by vault comics soon, was a pilot script she turned into comic, set in future where there’s a pandemic of organ failure, focuses on scientist that makes duplicate organs
• David schrader: short filmmaker, recently got baby bad-ass published
• Steve prince: self-publishing guru, six titles so far, including monster matador, set in a future where monsters have overrun humanity, travels world fighting monsters with sword and cape
• Jeff leeds: anthology guru, collections of short stories, easier to produce and cheaper, good way to wade into the water, by day, jeff is exec at nbc
• “What makes it the right idea?”
• “How do you get it into the hands of publishers?”
  • Need a cover, 6 pages of art that’s colored, inked, lettered
  • 6 pages is the min, more is better
  • Then need a treatment: the meat of the story, all the way through
  • Describe your team, list everyone’s experience
  • Need to be able to say “i know where this story is going”
  • Keep it short: no one wants a 60-issue series from someone they’ve never heard of; first arc of spencer & locke is only 4 issues
  • Karla: did five pages, no one would pick it up because they couldn’t see where it was going, so had to publish the first issue herself, find letterer and colorer via conventions, that helped her get a publisher; had a treatment for the first 15 issues, but publisher that picked it up only wanted to do the first 5 and see how they did
  • One place where having a finished book might hurt you would be with a company like Boom! Comics, who want you to use their own artists, and will want to edit it, etc
• Steve: primarily a writer, writing pitches, going to publishers, you’re waiting a lot, very challenging market, but printing is relatively cheap, comixology submit makes it instantly out there, if he has an idea he just does it, no waiting for others to sign off, people more likely to read comic book than a comic script
• Submission process for anthologies is a little different: a short compressed time window for submissions, instead of the eternal death march for regular issues; submissions process is going to be easier, will need pitch and character designs, not whole story
  • One example: theme was las vegas, sent in pitch, they asked for page by page outline, not a full script, and went from there
  • [but how do you find out about these anthologies?]
• Unless it says otherwise in publisher’s site, only email them
• There are really good fb groups connecting comics writers and artists, can use them to find people

Writing Great Dialog

• Merifred scott: writes comics and animation; including guardians of the galaxy and transformers, avengers, spider-man, etc
• Holly hukins: writes animation, usually comedy, first job was on rugrats (first season), story editor on recess, recently created some preschool shoes, now working on 8–11 comedies for amazon
• Jim: wrote a lot of scooby doo, wrote an episode of supernatural where the brothers are sucked into a scooby cartoon, producer and editor on green lantern animated series, etc
• “People from michigan are weird”
• Matt lane couldn’t be with us, has been having back problems
• Craig miller: written curious george, smurfs, beastwars, gi joe, done a lot of international market work
• How many of you are writers or want to be writers?
  • I feel so sorry for you
• Novels are very different dialog than comics or video games or animation
• Harrison ford to george lucas: “you can write this shit, but you can’t say it”
• What is it you keep in mind when writing dialog?
  • Meriford: make sure everyone has a distinct voice, a distinct pov; will go back through and read every line that a character has, all in a row, to make sure their voice is distinct; easy when writing back and forth to have the characters’ voices start to sound the same
  • Craig: every character should have a distinct speech pattern. Each line of dialog should tell you immediately when you hear it who it is
  • Jim: do your own personal table read to your family; read it out loud, always
  • Craig: there are lines that read just fine, but your mouth can’t say them
  • Holly: table read with the writing team is traditional on comedy shows, lets you punch up jokes and catch things like “you started each line here with the same letter”
  • Meriford: uses final draft’s text-to-speech feature to get robotic feedback on how well it works
  • Craig: people of different walks of life, from different parts of the country, speak differently
  • Meriford: definitely don’t want to distract from main character with weird dialog from the auto mechanic, but believes people talk the way they think. An auto-mechanic that thinks with their hands is going to speak differently than one that is very organized and thoughtful
  • Holly: actors really appreciate that. Love it when they can come in and use the dialog to figure out how to play it, because it sounds like how the character thinks and approaches the world
  • Jim: each format has its own constraints and needs; an 11-minute short, every line needs to drip character and be surprising in some way; for an hour-long piece, can let things breathe a bit more
  • Craig: in animation, things have to be happening, no one will watch really long scenes with lots of people talking; in comics can’t have soliloquies, have to keep things moving
• How do you come up with the speech patterns for distinct characters?
  • Meriford: i steal it; noticed female characters tend to fall into sounding the like the same “action lady”, pulled one character from tommy lee jones’ patterns in the fugitive; had one class where they had to ride the bus and listen, take notes, to figure out how people talked
  • Jim: You cast your story in your head, with actors that you’ll never get
  • Meriford: you can even steal little quirks, like how obama used to tell a joke during a speech, and then stop and comment on it, and it was such a dad thing to do
  • Jim: like in improv, you build a character around these traits and quirks, and then put them in situations; what would norman be like at the deli? Things like that
• Jim: what they don’t tell you, the introvert, looking for a job as a writer where you stay in a dark hole all the time, is that what you’re really signing up for is a lifetime selling your story to other people, and you have to become comfortable doing that
• Meriford: hardest part of being a dramatic writer is having to walk into a roomful of people
• How do you juggle between dialog that’s clear and not on the nose?
  • Jim: gotta hide it; to your ear, gotta sound like something someone would say; there are tricks, and everyone’s heard the backstory dialog that sounds weird
  • Meriford: three levels of dialog: first where you mean what you say (hello, i love you, duck), second is when you mean what you say, but you talk about it sideways (“it’d be a shame if something happened to that nice suit of yours”); third level is where you never speak about what you’re actually talk about (gene hackman talking about horses after getting demoted by denzel washington in crimson tide); don’t want to live in number 3 or number 1, want to bounce between 1 and 2; another number 2 example: the fight’s never really about the dishes, even though that’s what you talk about
  • Craig: if you do stop to have a conversation while the t rex is chasing you, it’d better be damn good dialog
  • Meriford: on the other hand, you can stop to have those moments, like hawkeye and black widow in the first avengers: “this reminds me of budapest” “you and i remember budapest very differently”; so much character and backstory embedded in those two lines
• Meriford: loves writing spiderman, because he talks through every fight, it’s a compulsive tick for him, so you never have to kill your darlings in that one
• How do you convey accents?
  • Holly: tries not to use accents, mainly
  • Craig: standard thing in scripts is to put in parentheses “has a german accent”
  • Jim: example, early mistake he made writing scooby was to actually write “rutt-roah”, actor took him aside and said “don’t do that; i know how to do the voice, if you put an ‘r’ in front of every word, i won’t know what it is”
  • Meriford: in print, especially, use a lighter touch with accents than you want to, it’s hard to read, maybe throw in a word or two from the language, or use the ol’ asterisk (translated from the chinese)
• What about characters written as cyphers? Like james bond, a bland character in exotic situations?
  • Meriford: tries to avoid writing bland characters, just as a rule
  • Craig: bond isn’t a cypher, he’s a job, is allowed to show some emotion but in few situations
  • Jim: jack reacher books are like that, he’s a machine, what’s interesting is the situations “the corruption goes a lot deeper than you think”; sometimes it’s not about the character, it’s the world, but the other people have to have a lot of character in their dialog
  • Meriford: if you’re gonna write a character with very functional dialog, give them a quirk or two to give that smooth line of dialog a bump or two, make it seem like they still have some depth

Writing and Illustrating Children’s Books

• Henry herz: moderating, three picture books coming this year; also does self-publishing
• Jenni holm: newberry award winner, three time
• Antoinette portis: will be here later; former creative directory at disney products; ny times bestseller
• Dan santat: ny times bestseller, caldecott award winner
• Deborah underwood: writes intersteller cinderella, supersaurus, here comes cat
• Eugene yelchin: newberry honor winner; haunting of falcon house
• What inspires your writing?
  • Dan: grew up watching 80s tv: a-team, falcon crest, airwolf, a lot of inspiration comes from borrowing other people’s ideas and making them your own, watches all kinds of movies, the weirder the better, anything to jump start his imagination, doesn’t shy away from anything that he might not be into
  • Jenni: pulls things from her own childhood, grew up in the 70s, middle child of five kids, only girl, read a lot of comics, late father was a huge comic fan, weaned on prince valiant and flash gordon, didn’t notice at first that weren’t a lot of women in comics, but when grew up wanted to see herself in comics, stole a lot from her own elementary school life
  • Antoinette: some from own childhood, some from daughter’s childhood
  • Eugene: so many ideas, so much information coming in, hard to decide which ideas to pursue, what he uses to choose between them is the emotion behind them and the strength of the idea, even if he has a poppy idea that would sell books, if he doesn’t feel anything about it, can’t write it, has to let it go
  • Deborah: quiet book inspired by sitting at concert, waiting for it to start, noticed the different qualities of the silence that the crowd went through; for her the common thread is ideas coming out of quiet or out of play
• Questions from the audience: How many pages?
  • Picture book age: golden number is 32 (dan), if you add to it, you add by 4
  • Henry: fictional picture book, you’re looking at 500 words
  • Can find templates online to give a sense of the layout
• All endorse society of children’s book writers and illustrators, chapters all over
• Best book experience?
  • Deborah: new york children’s musical theatre group made her book into a musical, she got to go to new york and see her characters up on stage
  • Eugene: differs with every book, each book is its own world, living in that world for a time, is its own special experience
  • Antoinette: wanted to make her own art, her own property, after working for corporate masters for so long, ran away from disney, everyone thought she was crazy, but felt so good to get away and do her own thing, create her own art
  • Jenni: her son always read other books, had to do a book report on a newberry award winning author, left his book at school, she pointed him to her book, got him to write a book report on her own book
• Audience question: as an artist how do you get on a publisher’s radar?
  • Antoinette: If you join the scbwi, it’s very helpful with all that stuff; can send postcards and have a web site, your target audience is editors and publishers, who are the ones that do the hiring of illustrators, not writers
  • Dan: you’d be surprised who’s looking at websites
• Audience question: what do you think about self-publishing?
  • Henry: it depends on what you’re trying to accomplish; have your own timeline, own creative control, trad publishing is slow; downside is you’re responsible for everything, so either need to be a master at everything, or have a team that can be masters at everything; too often can see people rushing to self-publishing because they want to see their names in print, and don’t want to spend the time honing their craft; don’t think of it as a shortcut around traditional publishing, because the quality won’t be there
  • Antoinette: getting your self-pub book into a bookstore is a full-time job on its own, and as a creative person it’s probably not a job you want to take on
  • Dan: contra that, there are people that like the hustle, so even though they’re talented enough to be trad published, they choose to be indie
• Audience question: proper approach for submitting manuscript if you’re not an author?
  • Deborah: if you’re just an author, double-spaced typed manuscript is fine, if you’re an illustrator and you submit art, it’s a red flag for publishers
  • Eugene: so much depends on the art, better to submit without art
  • Henry: cover letter is typically three paragraphs: what’s the story about, market potential, bio stuff
  • Jenni: industry is more agented now, so becoming standard practice for publishers to not accept unagented manuscripts
  • Henry: true for the big five publishers, but for the medium sized and small pubs, they’ll still accept unsolicited submissions
  • Deborah: also, some publishers will accept unsolicited manuscripts from people that attend certain conferences
  • Dan: some graphic book publishers will even do “new talent” events
• Audience: why prefer children’s books as a medium?
  • Dan: had a cartoon show on disney for three seasons, dealing with executives is a pain in the butt, whereas in children’s publishing, an editor will endorse your views and your voice, your perspective is more intact in children’s publishing
  • Eugene: also comes down to your personality; if you’re more comfortable working in a team, than by yourself, then you’re going to drift into different media
  • Antoinette: knows an author/illustrator that is constantly pitching shows, wants to be in tv and movies, and to her it sounds like hell, don’t make as much money in children’s publishing, but you have more creative freedom, so it’s worth it
• Audience: how has having children affected how you write children’s books?
  • Jenni: they kind of ruin it, actually, productivity went into the toilet; i don’t think you need to have kids to be a children’s author, got her start before she had kids; in fact, recommend not having kids often
  • Deborah: i don’t have kids, and that’s why i have time to write; people write for the age of the kid they actually are, so i’m 6
  • Dan: kids help me become a better writer, because my memories of being a kid are a little skewed, thought was writing with things for himself as a kid, but then had kids, and realized he’d forgotten so much; had to re-discover his childhood through his kids
• Audience: do you see a dramatic change in how you do things with tech?
  • Jenni: kids are growing up so fast now, feels like there’s a renaissance going on in comics for children
  • Dan: thinks the attention span for kids is shorter; take a book like jumanji, that’s 4,000–5,000 words, couldn’t get something like that published today; if you’re pushing 700 words in a picture book, you’re already getting word-heavy
  • Antoinette: counter to kids’ attention span being shorter, is that they are way more sophisticated visually, don’t have to show every step anymore like you used to
  • Eugene: but even grad students these days don’t focus on an image like they used to, we have so much coming at us that we don’t stop to study anything and read an image properly
  • Antoinette: but kids spend so much time with a book, memorizing it
• Audience: appeal to parents first or kids?
  • Dan: flip flops, just tries to make a good book
  • Jenni: writes middle grade, she writes for the kids
  • Antoinette: my 4–5 yr old is dictating what works and what’s funny, want it to not be stupid, for the adult that’s going to be reading it
  • Eugene: little kids don’t buy for themselves, but older kids do, so it’s two different modes; i write for myself as the kid that i was, mostly write for 10–12; thinking about other kids and other teachers would make him too worried
  • Deborah: agree with writing for the inner kids; also likes to put things for the adult reading it that they can chuckle at that the kids won’t get

Inside the writer’s room

• Mark: show runner for the librarians
• Gab stanton: vampire diaries, the flash
• Michael morducci: vampire diaries
• Ryan cordel:
• Ashley miller: fringe, black sails, thor, x-men first class
• Steve melching: star wars rebels, clone wars
• Kay reinalt: twisted, free-form, freakish
• Marc bernarden: alphas, castle rock
• Amy berg: counterpart, da vinci’s demons, eureka
• Chris parnell: co-president of sony pictures studios, worked at sony for fifteen years
• Focus on the awesome task of writing in a writer’s room, a team work, and the writer’s room as a living organism
• What’s inspiring you on tv
  • Amy: obsessed with the good place
  • Marc: also watching the good place, because he does everything amy says, also watching jessica jones season 2
  • Kay: also watching jessica jones season 2, loves it, waiting for the last season of the best show ever, the americans
  • Steve: watching a lot of weird comedies, like another period
  • Ashley: catching up on shows that everyone else has seen, recently discovered community, watching now and it’s perfect in every way: marvellous ms maiselle
  • Ryan: not a comedy writer, but love’s Love on netflix, gets LA completely right, also loves the crown, looking forward to the terror
  • Michael: handmaid’s tale is awesome, wormwood about mk ultra is amazing
  • Gab: the one dirty secret they don’t tell you is that once you work in tv, you no longer have time to watch tv anymore; check out no activity on cbs because it’s surprisingly good
  • Mark: rebels just wrapped up its four-year run, it’s like the breaking bad finale of animation; we binge everything sucks, it doesn’t suck
  • Chris: end of the fucking world is also great
• Philosophy behind a writer’s room: impossible for one person to crank out all the material needed for a series; but lots of studies that argue against group brainstorming, that more creative work comes out of one person
• How important is a good showrunner to a group think session?
  • Kay: most important; if you’re trying to tell a single season story, have to have a strong point of view
• What does it take to be a good showrunner?
  • Chris: movies -> director runs it, writer is just one component; tv -> opposite, writer-driven medium
  • Amy: is really about surrounding yourself with the right people, need the right mix of personalities and skill sets, when you’re hiring crew, need your department heads to be great facilitators, can’t really go it alone and get the job done well (see true detective season 2)
  • Gab: have to manage people, have to manage a ton of money, have to manage all these writers, have to make decisions about all the costumes, etc, have to be the kind of person that can go to someone and say “help me out with this” and be open to what they have to say
  • Marc: have to be able to communicate what your objectives are, so others can march in the right direction and get it done
  • Ashley: best showrunners remind him of the best teachers, a lot of those skills convey, personality type that needs to walk into the room with a plan, but know the plan is going to change as soon as it encounters other people, not quite egoless, but have to let people talk and give them permission to be wrong; it’s a hard skill to teach people that just want to work alone in a dark room
  • Kay: showrunner has to protect the writing staff, has to make the room a safe place for everyone to be able to contribute
• Michael: thinks what makes the best writers who they are is courage and empathy; that’s also what makes a good boss; don’t want to scream at people if they come up with a not-great idea that moves the show forward, because then you won’t get their best
• Recommended: john cleese on creativity; find the video on youtube, it’s great
• Chris: and yet, you’ve got to hold everyone to creative standards in the room
• Michael: agrees, but don’t want to scare people, make them afraid to bring up ideas later on
• Steve: and sometimes, those crazy, bad ideas you pitch lead to the good ones, you laugh about it, and then it frees you up to think of the good one
• Gab: vocab about it, “this is the bad version, but…”
• What kind of structure do you impose?
  • Amy: law of diminishing returns, happens early in the afternoon, comes in with an idea of what she wants to get done, and if she gets there, she gets there, sometimes you have to be willing to call the brainstorm session over and move on
• When breaking season down, use a board, index cards with different color for each character, writer’s assistant is writing everything down, nice feeling that something’s being done because you have a physical object at the end of the day; break down the season episode by episode, or arc by arc
• How do you build a team?
  • Mark: be as brutal as you can, until you tell me i can’t change it anymore, and then tell me it’s brilliant; there’s a real value in criticism, if you can trust that everyone is working toward the same goal, you want to make it better
  • Chris: have to be able to take a note, to teach people how to take notes
  • Michael: was told by a showrunner, most tv writers are not very good, his job is to let them take the script as far as they can, and then come in and make it better; on vampire diaries, they put all the character names in a hat, and everyone had to pull a name, and they became the advocate for that character, kept them from dropping the ones they weren’t as excited about
  • Marc: have to be willing to remember that you’re getting paid to not get everything you want, you’re not always going to win, and you have to be willing to accept that, and move on
  • Gab: writing tv is really about mimicry, because you have to be able to write in the voice of the creator of the show; when she was coming up, you had to write a sample episode, and that proved you could fit into the show; today everyone’s writing their own pilots, and that shows they can write, but not that they can do the work in the writer’s room on the show
  • Mark: “just because you can write hamilton, it doesn’t mean you can write ncis: des moines”
• Ashley: any a-hole can be an artist, the hard part is being a craftsperson, showrunner has to bring an understanding of the craft into the room, and how to use the craft of the writers in the room; pitching responsibly means having an awareness of what the consequences of the idea will be both for what came before and for what comes after; best defense against terrible ideas is “tell me about”, it’s still notes and criticisms, but a different way to think about it, opens people up instead of shutting them down
• Amy: worries that if you have to come to the room with such a complete idea, you won’t bring it, she’s good at ping-ponging off of ideas that are very small grains of things
• Kay: very important when you’re doing it for the first time, that you feel comfortable and not stupid, even when you’re still learning your craft
• Marc: what he wants from a showrunner is the same thing as from a dungeon master; some idea of where you’re going, but the ability to shift things on the fly as the players throw monkey wrenches into things, give them agency in the game; a good DM will roll with the players moving off of the main storyline, and find a way to incorporate it into the main arc

Intro to TV Writing: first draft to staffing

• Possible questions:
  • Previous panel talked about shift from writing episode for the show on spec to writing your own pilot; which is better?
  • How much of the show do you need to have worked out when pitching a pilot?
  • Better to get a gig writing on a current show before pitching your own?
  • Agents? Needed or not needed?
  • Where do you send these scripts? How do you know which shows/editors/producers might be open to them?
• Melissa: wrote for lost, the gifted, veteran of the warner brothers workshop
• Cat: being human, the cape, cw’s arrow, legends of tomorrow
• Drew: marvel’s agents of s.h.i.e.l.d., buffy, arrow, warehouse 13
• How do you go about spec’ing a script of an existing series?
  • Melissa: don’t write for a show you don’t like, it’ll be terrible; watch all the episodes so you don’t do something they would never do; watch a show with a legal pad and do a break down of the show minute by minute, the pacing, how it’s put together
  • Cat: seconds everything she said; first script ever spec’d was lost, tried to make it as much as a contained story as possible, found some plot holes she thought she could fill out; try to find that space to work in that’s self-contained; but also find a way to orient readers that might not have seen the show; she did a “previously on lost” to let reader know where everyone was and what’s going on; everyone said she was crazy to spec lost, but that’s how she got a job on the verge
  • Drew: wrote an ally mcbeal and a sopranos, and a buffy spec, had a meeting with an exec of 21st century fox, they showed it to joss whedon, which is a NO NO
  • Rule: you don’t show the spec you wrote for the show to the actual showrunner, not only will they immediately spot all the flaws, but for legal reasons they can’t read it (might be accused of stealing ideas from it)
• Purpose of writing a spec is to show you can write in the voice of the show
• Dangerous to write a spec for a show that’s been around a long time, because it could vanish, then you’re screwed
• What are you looking for in a script?
  • Cat: ex: for a superhero show, not just looking for superhero writers, right now looking for humor, and writers who can write emotional moments, arcs are very important for them; snappy dialog also great; period piece for a time-travel show; humor and heart
  • Melissa: when reading for vampire diaries, looking for genre scripts, but in a wide range; had to be able to write banter, since it was so critical to the show
  • Drew: it’s character, emotion, and humor, just like cat and melissa said; for example, on agents of shield, they’re all comic book geeks, got that covered, what they’re looking for is emotion, can you write it, can you inspire it?
• Original pilot talk: heard eps lately say they want to read the pilot, others just want the spec
  • Melissa: wants to read the pilot, tells you a lot about who the person is; when go into a meeting, they want to get to know you and figure out who you are as a person; even if you don’t get the gig, it’s not always about you, don’t ever take it personally; when she goes into meetings, starts with the story about why she became a writer
  • Drew: when writing pilots himself, he’s known for comic book shows, so will zig instead of zag, write a family drama; he’s looking for in a pilot is writers that can do some good worldbuilding, present a fully-formed world from the get-go; no place to hide in a pilot
  • Cat: when writing a spec pilot, really take a hard look at your dialog; showrunners will skip prose and go right to the banter, because they’re busy; what separates a good writer from a great writer is finding those voices and channeling them in a way that’s distinct; make it so it sounds like only those characters could sound that way
  • Melissa: harder bar: should be able to say at the end of the pilot: what’s the series? You should have questions, you should get to the end of the pilot script and immediately want to know what’s coming next, and know what sort of questions are going to be coming, what’s the underlying engine of the story
• Audience q: How can get writing to people like them?
  • Drew: the best way is to have an agent, or a manager; need to network, go to writers events in LA, don’t cold-call them, meet them that way
  • Melissa: if she had unlimited resources, would invite a group of writer’s assistant’s out to drinks, find out who needs people
• Audience q: why write a spec script if you can’t show it to the show?
  • Cat: main purpose is to get into any of the writer’s programs for the networks, warner brothers, nbc, fox, etc, all of them need a spec script as part of the application process; also EPs will read spec scripts later on
• Audience q: how much map out for the series when pitching pilot?
  • Melissa: you don’t have to show anything, but as a writer, it’s a good thing to know the big signposts, what’s going in to season two, etc; ed solomon: don’t do it for the money, or the credit, or the fame, do the work, the rest will follow; it seems easy, but it’s not
• Audience q: if a show gets cancelled, does that kill the spec scripts for it?
  • Yes
• Audience q: what’s the biggest oopsie you’ve ever made and how did you get past it?
  • Melissa: do a lot of research on the person you’re going to meet when going into a staffing meeting; know whether they’re casual people or formal, so you know how to dress, how to approach them
• Audience q: biggest takeaway from first season staff writing?
  • Cat: learn how to write on whiteboards, like practice, and get really good at it, because that skill will be enough for you to stay in the room, they’ll keep you just for your ability to write legibly; if you have good board writing, they will love you
  • Drew: really lucky that his first staff job was writing with buffy; once you get into the room, have to be ready to shift your skillset to working with a roomful of (potentially) geniuses; when you’re building a story with other people, it’s like a train, once it’s building momentum, if you’re the person that just says “no, that’s crazy” then you’ve just pulled the emergency brake on the train, no one likes that; gotta learn how to work with people and introduce things gently
  • Melissa: should have been more comfortable in her own skin; surprised by how miserable she could be doing the thing she had worked so hard to do; wasn’t quite the right fit for that staff room, and made it worse by being incredibly awkward; should have done some meditation and relaxed so she could enjoy having made it
• Audience q: elaborate on the fellowship?
  • Cat: replicated feel of the writer’s room, ten people total, all pitching specs to each other, getting feedback; going through very organized process of outline, then vomit draft, then revisions; half of the program was writing, the other half was the business; practice going to general meeting, execs would come in and talk about what they want from writers, etc; got a speech instructor who told them how to speak in public; even had showrunners come in and talk to them; started out as a novice: one tv spec and one pilot; had two more scripts when she was done, and felt ready for a writer’s room
• Audience q: biggest mistakes you see in tv pilots? How about submitting artwork?
  • Melissa: notices people overcomplicate things, ten pounds of story in a one-pound bag; simple idea executed well carries a lot more in the read; ask a friend of yours that you consider a little dense to read it and see if they can make it out
  • Drew: if you need art to back up the script, then you’re failing a bit, since the spec’s purpose is to show you can build the world with just the script
• Audience statement: animation caucus has monthly meeting where they do events with professionals coming in
• Audience q: if you have a pilot, what do you do?
  • Cat: same thing
  • Melissa: if you want to pitch it to a network, helps if you can find an actor who’s interested, will get them to answer the phone, at least
• Audience q: final polishing?
  • Cat: writer friends, use them; writer’s groups can be so helpful; friends get on shows, and then they recommend you, and give you advice
  • Melissa: do a table read; find actor friends if you can, but even if not, just get friends together and have them read it, because you can discover things you missed

I did it! Wrote 1,586 words this week, just enough to make my new goal :)

Novel’s passed 10,000 words, and is still chugging along. So far, so good.

And this kind of pace feels good, too. Not too intense, but not so slow that I don’t feel like I’m making progress. And each week, I get a reward, a visible reminder of how much work I’ve done.

Many thanks once again to Scott Sigler, for hosting that Writers' Coffeehouse weeks ago, and sharing his scoring system with us. It’s really helped me, and I’m grateful.

And now, to pick out some new music! Last week I grabbed Monster Magnet’s Powertrip, an old trippy-rock-meets-cthulhu album that I missed owning. This week I’m considering picking up something from The Stooges, another classic band I haven’t heard a full record from.

Another week, another push. 1,265 words written this week, again just over goal.

I think it’s time to boost my numbers. Next week, I’ll shoot for one extra page, making it 1,500 words for the week. That’s still only 300 words a day, Mon-Fri. Should be doable.

Gotta earn my weekly music :)

And if it’s not doable, well, then I’ve got my penalty waiting for me. Not that I ever want to experience it.

I did end up picking the Black Panther soundtrack last week. I think it’s a little uneven, but still solid (unlike the movie, which I thought was great).

This week…who knows? Maybe time to pick up something I missed from last year.

I did it again! 1,488 words written this week. The streak continues!

The iPad continues to earn its keep, letting me write on my last day in Tahoe and while on the road back to San Diego. Even discovered Scrivener for iOS' hidden word-count tracking feature (hint: tap the displayed word count for a scene while having it open for editing) and used it to make sure I hit my daily targets.

New novel’s at ~8,500 words total, most of those written under the new scoring system. I think I’ll keep it :)

As for music, last week I ended up snagging Ladytron’s Light + Magic, another older album from a band that I’d never listened to before (yes, I rely on the AVClub for a lot of my music recommendations. don’t judge me). This week I’m thinking of picking up the Black Panther soundtrack, since I just saw – and thoroughly enjoyed – the movie.

Still on the road. Got back from the cruise last Sunday, unpacked, did laundry, then re-packed everything to fly to San Francisco on Monday.

Whew.

I was in SF for a work conference till Friday, when they packed us all in buses and shipped us up to Lake Tahoe.

Sounds glamorous, but it wasn’t. We got caught in a snowstorm, and they shut down the main road into Tahoe. Our bus was lucky: it only took us 7.5 hours. Others took 12.

So I went from Baja sunshine to SF gloom and rain to Tahoe’s freezing heights. Oh, and I got food poisoning the next day.

But I got my writing done, dammit: 1,265 words written, the last few hundred pounded out between trips to the bathroom to throw up.

I’ve effing earned this week’s music, dammit.

I’m on a boat!

I don’t have internet access while at sea, so I’m posting this on Thursday, while we’re in port at La Paz, Mexico.

I’ve still managed to hit my weekly writing goal, though, thanks to my (rapidly becoming trusty) iPad :)

Total words: 1,276

No idea what album I’m going to buy as my reward. Last week I ended up grabbing another blast from the past, Orchestral Movement in the Dark’s Dazzle Ships.

I hear the Black Panther soundtrack’s really good…I might pick up that (once we get home).

Second week of using my new writing score system. Managed to turn out 1,489 words for the new book, so I exceeded my goal (again)!

I rewarded myself last week by buying Bauhaus' Burning From the Inside. I’d heard of Bauhaus for decades, but never bought one of their albums before, and this article from the AV Club got “She’s in Parties” playing an infinite loop in my brain. So I took the plunge (and the album’s great, btw).

This week I’m thinking of buying something more recent. Not sure what yet, though.

I’m writing over 300 words most days, so I’m thinking of upping my goal, to 6 pages a week, or 1,500 words. I’m about to do a lot of travel over the next few weeks, though – one week on a cruise for vacation, ten days in Northern California for work – so I think it’d be best to wait until after that’s over. 1,250 words a week is going to be hard enough to hit when I’m on the road.

If we designed doorknobs the way we design software, each one would come with a user manual.

They wouldn’t be guaranteed to work. You could spend hundreds of dollars on a new doorknob, only to find the handle doesn’t turn, and the manufacturer doesn’t offer a warranty.

Your doorknob would have options for direction of turn, speed of opening, and click sound, but not shape or color.

Most doorknobs would be sold without locks. You could get a knob with a lock, but it would be $10,000.

Each door in your house would need a different doorknob, depending on what year it was built. Doors from 1994 would need completely different knobs than 1993 doors. Sometimes you’d be able to put a 1995 knob in a 1993 door, but not always.

Modern doorknobs – made only for modern doors – would understand some voice commands, like “What time is it?” and “When did you last close?” But only from one person in the house, and the commands for opening and shutting would be different depending on which knob you bought and which door you installed it in. Most of these voice doorknobs wouldn’t have handles, at all.

Some people would lay awake at night, wondering if our doorknobs were getting too smart, and would one day rise up and kill everyone.

After attending Sunday’s Writers Coffeehouse, I decided to adopt Scott Sigler’s suggestion of a scoring system. Thought it’d be a good way to push me to get back in the writing habit, after the fiasco that was the last few months.

I decided on the following:

• A goal of 1,250 words a week. That's five pages total, or one page a day if I write every weekday.
• Words on the new novel count full. Words for professional or marketing writing (query letters, etc) count half. So a page of query letter writing equals half a page toward my goal.
• I can't check the news, or do chores, or pay bills, or anything I usually do in the morning, until after my word count for the day is met.
• If I hit my weekly word count total, I get a reward: buying a new music album. I love getting new music, and albums are cheap enough now that I can buy one once a week and not break the bank.
• If I don't hit my weekly goal, I get a punishment: no beer or wine for a week. I'm a big craft beer guy, so this hurts: no more pairing a nice IPA with some fish tacos, or a tiramisu with a coffee stout.

As a result, I’m writing about 300 - 400 words a day, not 250, so I hit 1,554 words yesterday. If I sustain that pace, I’ll need to up my weekly goal.

So hooray for me! I’ll be getting some new music this week :)

Attended my first Writers Coffeehouse in a few months yesterday. I’m glad I did; I came away feeling more like a “real” writer, connected to a community of fellow writers, than I have in a long while.

Plus, our host, Scott Sigler, gave us a system for tracking our progress week by week that I think will help me with my current novel.

Many thanks to Scott Sigler for hosting, and to Mysterious Galaxy for letting us hold it in their (frankly awesome) store!

My notes from the Coffeehouse:

• sports in stories: do enough research that you can color in the character; less detail is more: more detail is more chances to screw it up for people that know it; be specific, but drop it in and move on
• vocal tick, physical mannerism, first name last name: stephen king's technique; uses for secondary characters as a flag or anchor for readers; establishes it all in one paragraph, then uses throughout
• the scorecard: set a weekly goal, meet it, challenging but doable, set consequences if you don't make it (scott loses a bass from his collection for two months)
• not sure what to do? write a short story. you'll accomplish something, and if your brain is distracted by something, that's what you should work on next
• scott sigler: "how to write your first novel" on youtube: unorthodox writing advice
• his scoring system is based on a page: 250 words.
• when writing first draft, it's pure words produced
• second draft: each word counts for half, so double the word count goal and achieve that
• third draft: each word only counts one third
• calls with editor, agent, etc: counts for half (ex: 1,000 words an hour means a half hour phone call counts as one page)
• what about research? doesn't count. research doesn't pay the bills
• characters, relationships, conflict: all that matters. do just enough research to enable the writing. that's it
• research trick: find and read a kid's book on it; they've distilled it all for you
• outlines? depends on how much you use them. if you do: single-spaced, count each page of outline as a page, timebox the work (ex: 2 weeks to get the outline done)
• another reason to put off your research: sometimes only when you get to the end do you know what you need to research (backspackling the grenade needed in chapter 30)
• query letters? that's business, so half-count; set a reasonable goal, like one query letter per week (that's twelve queries in a quarter, not too shabby)
• and track what you've done: on paper, or todo lists, or however, but record your daily work, and total it at the end of the week
• when you make it: celebrate it!
• beta-readers? prefers finding serious readers, not writers. why? TWILIGHT
• best reader is you. take the book, let it sit for six months, come back and read it. you'll see what you really wrote instead of what you thought you wrote
• reedsy.com: site for finding freelance editors; sigler uses it (but do your research, interview them, etc)
• POV shifts: helps show different aspects of the characters, by giving insights from one pov character about another
• tension: a daily chore that if not done causes trouble (the shining: he has to release the pressure from the boiler every day; lost: they have to go down and push the button every day or else); good way to put a ticking clock in your story
• prisonfall: have the characters in danger from the start, use dealing with that as a way to do your world-building
• muse gone? go write a shitty short story; go write some fan fiction; do something else and come back to itp
• recommends putting first book of a series out for free to start out, to get it in the hands of readers, so you can find your audience
• save the cat: great screenplay writing book, woth chapters about elevator pitches
• attendee recommends donald maas' workshop; went last week in irvine, learned a lot
• don't be afraid to say no when you get a contract from a publisher; hold onto all the merchandising, film, etc rights you can

Not what I expected. I’d always thought the Meditations was a set of philosophical aphorisms. Instead, it’s something between a diary and a daily “deep thought”, a recording of a conversation an Emperor of Rome was having with himself.

As such, it’s repetitive and very personal, and yet somehow still relevant, hundreds of years after it was written.

Three things I found useful:

• Try to learn from everyone, even (especially) the ones you disagree with.
• If you know someone’s a jerk, don’t expect them to treat you fairly. And definitely don’t get angry with them for it, since you knew who they were from the start.
• Success and failure happen to everyone, over and over again. So there shouldn’t be pride in the former, or shame in the latter.

Not what I expected. Written in plain language, as if he wanted to sound trustworthy, so the reader wouldn’t notice the (non-glorious) things he skips over.

Fascinating to read now, after I know more about both what happened to Caesar afterwards and the Gauls he attacked.

Three things I learned:

• Caesar’s mercy started during the Gaul campaign, when he’d often pardon former enemies that were willing to bend the knee.
• Caesar justified his attacks on the rest of Gaul and Germany on a domino theory: if the Germans prospered in Gaul, he said, they’d eventually march on Rome itself.
• The Pullo and Vorenus from HBO’s Rome were based on real people, that Caesar wrote about by name (!)

Illuminating. Everitt makes Augustus a sympathetic figure, but without hiding any of his flaws: his hypocritical championing of family values, his slaughtering of competing Roman families, his unforgiving behavior towards his own family and friends. And he shows how Augustus' life was often a series of serious mistakes followed by lucky victories, not a steady calculated rise to power.

Three things I learned:

• The idea of having two "co-emperors" of Rome goes back to Augustus. He often had at least one trusted friend or family member invested with equal power and sent to rule different regions of the empire.
• Augustus' first official post was religious: his great-uncle Caesar, got him appointed to the College of Pontiffs, who were in charge of performing public sacrifices
• Augustus was called "Princeps", not Emperor. He was careful to keep his powers legal, renewed periodically via legislation, and to act humble while in Rome

Today’s the first day of NaNoWriMo!

I’ve got a rough outline, written short stories about three of my main characters, and filled in most of the setting.

Time to get cracking.

Essential. Maas describes the elements of a “breakout” novel, showing how to make any plot or story more compelling. He pulls examples from recent (well, recent to the year 2000, which is when the book was written) novels to illustrate each of his points, and even has exercises in each chapter you can do for your own novel.

I’m already mixing in his approach as I prepare for NaNoWriMo. It’s given me another set of questions to ask about my characters, plot, and setting, to help me push them to a higher level.

Three things I learned about writing:

• People have been talking about the death of the mid-list since the 1970s. Don't let it phase you.
• Escalating stakes doesn't mean making the one danger greater. It means adding more, different, dangers for the protagonist.
• Characters need to be larger-than-life. Find the extraordinary in ordinary people, and bring that to life.

Masterful. It’s a classic for a reason: a locked-room mystery on an entire train, that builds slowly through lie after lie until the truth comes rushing out all at once.

Damn, but Christie was good.

Three things I learned about writing:

• Skip over the dialog that doesn't matter. Sometimes it's enough just to say "so-and-so made a suitable response."
• Even adventures that get stumbled into have to be driven by the protagonist's choices. Poirot doesn't ask for the mystery, but he deliberately pursues it to the end, because that's who he is.
• Put the description at the start of the scene, briefly. If the position of something isn't important, leave it out. It's enough to report that "there were pencils and paper," we don't always need to know exactly where everything is.

Realized a few weeks back that I wasn’t making the progress on the short stories that I wanted to. And I wasn’t making any progress on editing the second novel.

And NaNoWriMo is coming.

At first, I made the usual excuses to myself – I’ve lost my morning hour to write, I can catch up on the weekends – but I knew the real reason: fear.

Fear that I wasn’t going fast enough. Fear that I wasn’t writing stories that were good enough. Fear that without an hour to write in, I wouldn’t be able to get anything done.

So I’ve gone back to an old habit: write every day. I have a reminder in my phone, a little task that I can only check off when I’ve done some writing that day.

How much doesn’t matter. 100 words, 250 words, 400 words, don’t care. So long as I write something.

And it’s working. I finished the first draft of one short story early this week, and I’ll have a draft of a second story finished this weekend. When those two are done, I can start planning the NaNoWriMo novel.

So I keep telling myself: Step by step, day by day. One word at a time.

What Went Wrong

And yet. There were some plot points that didn’t quite add up for me. Some sour notes in this otherwise perfectly bittersweet symphony of a movie.

Take Jared Leto. No, I mean take him away, please. He’s too young to be playing the character of Wallace, who, if he was saving the world in the mid–2020s, should be in his mid-forties by the time the movie starts. Leto sports a beard, true, but that doesn’t make him look any older. Instead, he looks like a kid that shaved off his dad’s beard and glued it on backwards. Threw me out of the setting every time he was on-screen.

Then there’s the rebels. They pop out of the woodwork late in the third act, and we’re supposed to believe they not only have a plan for a rebellion, but they’re about to execute it…if they can just…get…more…time. And that requires killing a human that doesn’t know anything about them? Because any knowledge Deckard may have had is about three decades out of date.

Finally, Joe’s “conversion” to the rebel cause is a little sudden. Their leader gives him at the end is just a few sentences. Too slender a reed to hang a turncoat on.

How to Fix It

Fixing the rebels is harder.

The simplest way would be to just drop that plot thread altogether. It’s only given a few minutes of screen time, and it’d be just as convincing for them to be concerned for the child on its own merits, as well as worried about what Wallace will do if he masters replicant reproduction (a line like “Imagine it. An infinite number of slaves, living forever, never their own.” would fit in fine).

But I think the best way would be for the rebels to reveal to Joe that there’s not just one replicant child. During Freysa’s “join us” speech, she explains that Rachel and Deckard’s baby was just “the first of many.” She steps back, and we get that overhead shot of Replicant after Replicant standing there, all about Joe’s age. Freysa explains that once Rachel and Deckard showed it could be done, they made others, and hid them, too.

And there’s more: because they had real childhoods, the second-generation Replicants can pass the Replicant tests as human. They’re free.

When they have enough for their own off-world colony, they’ll pick some new planet and settle it themselves: a new world, where no Replicant will ever be a slave, ever again.

But that dream will be destroyed if Wallace gets his hands on that first child.

That’s the cause that Freysa and the others were willing to die for. Not one child, but many. Not some far-off rebellion, but a long-waited-for escape.

A cracking good read. Illuminates the relationship between Gen X and Gen Y, something that’s always felt a little slippery to me (as someone born in 1979, often thrown in with the Millennials but identifying with Gen X).

Filled with moments that made me nod along (the movie list for Gen X), and others that showed me a corner of the 90s I didn’t know existed (Sassy magazine). The book was clearly a work of love for both Eve and Leonora, and it shows.

Three things I learned:

• Titanic was a huge movie for Gen Y. What I remember as just solid Oscar-bait was apparently perfectly tuned to imprint on young Gen Y brains.
• Clueless can be read as not just a great adaption of Emma, but also as a love story between Gen Y (Cher) and Gen X (Josh), reflecting the complicated relationship between the two generations.
• Complaining about the current tech-driven dating scene is common to Gen Y, though none of them would want to go back to the way things were before.

It was a good Conj. Saw several friends and former co-workers of mine, heard some great talks about machine learning, and got some good ideas to take back to my current gig.

There were some dud talks, too, and others that promised one (awesome) thing and delivered another (boring) thing, but overall it’s inspiring to see how far Clojure has come in just ten years.

My notes from the conference:

DAY ONE

KEYNOTE FROM Rich Hickey: Effective Programs, or: 10 years of Clojure

• clojure released 10 years ago
• never thought more than 100 people would use it
• clojure is opinionated
  • few idioms, strongly supported
  • born out of the pain of experience
• had been programming for 18 years when wrote clojure, mostly in c++, java, and common lisp
• almost every project used a database
• was struck by two language designers that talked disparagingly of databases, said they’d never used them
• situated programs
  • run for long time
  • data-driven
  • have memory that usually resides in db
  • have to handle the weirdness of reality (ex: “two-fer tuesday” for radio station scheduling)
  • interact with other systems and humans
  • leverage code written by others (libraries)
• effective: producing the intended result
  • prefers above the word “correctness”, none of his programs ever cared about correctness
• but: what is computing about?
  • making computers effective in the world
  • computers are effective in the same way people are:
    • generate predictions from experience
    • enable good decisions
  • experience => information => facts
• programming is NOT about itself, or just algorithms
• programs are dominated by information processing
• but that’s not all: when we start talking to the database or other libraries, we need different protocols to talk to them
• but there’s more! everything continues to mutate over time (db changes, requirements change, libraries change, etc)
• we aspire to write general purpose languages, but will get very different results depending on your target (phone switches, device drivers, etc)
• clojure written for information-driven situated programs
• clojure design objectives
  • create programs out of simpler stuff
  • want a low cognitive load for the language
  • a lisp you can use instead of java/c# (his common lisp programs were never allowed to run in production)
• says classes and algebraic types are terrible for the information programming problem, claims there are no first-class names, and nothing is composable
• in contrast to java’s multitude of classes and haskell’s multitude of types, clojure says “just use maps”
• says pattern matching doesn’t scale, flowing type information between programs is a major source of coupling and brittleness
• positional semantics (arg-lists) don’t scale, eventually you get a function with 17 args, and no one wants to use it
• sees passing maps as args as a way to attach names to things, thinks it’s superior to positional args or typed args
• “types are an anti-pattern for program maintenance”
• using maps means you can deal with them on a need-to-know basis
• things he left out deliberately:
  • parochialism: data types
  • “rdf got it right”, allows merging data from different sources, without regard for how the schemas differ
  • “more elaborate your type system, more parochial the types”
  • in clojure, namespace-qualified keys allow data merging without worrying about colliding schemas (should use the reverse-domain scheme, same as java, but not all clojure libraries do)
  • another point: when data goes out over the wire, it’s simple: strings, vectors, maps. clojure aims to have you program the same inside as outside
• smalltalk and common lisp: both languages that were designed by people for working programmers, and it shows
  • surprisingly, the jvm has a similar sensibility (though java itself doesn’t)
• also wanted to nail concurrency
  • functional gets you 90% of the way there
• pulled out the good parts of lisp
• fixed the bad parts: not everything is a list, packages are bad, cons cell is mutable, lists were kind of functional, but not really
• edn data model: values only, the heart of clojure, compatible with other languages, too
• static types: basically disagrees with everything from the Joy of Types talk
• spec: clojure is dynamic for good reasons, it’s not arbitrary, but if you want checking, it should be your choice, both to use it at all and where to use it

• inspired by the gin rummy card game example in dr scheme for the scheme programming language
• found the java.awt.Robot class, which can take screenshots and move the mouse, click things
• decided to combine the two, build a robot that could play gin rummy
• robot takes a screenshot, finds the cards, their edges, and which ones they are, then plays the game
• lessons learned:
  • java interop was great
• when clojurescript came out, decided to rebuild it, but in the browser
• robot still functions independently, but now takes screenshot of the browser-based game
• built a third version with datomic as a db to store state, allowing two clients to play against each other
• absolutely loves the “time travel” aspects of datomic
• also loves pedestal

• using clojure for about two years
• developed toolkit for doing bayesian statistics in clojure
• why clojure?
  • not as many existing tools ass julia or R
  • but: easier to develop new libraries than in julia (and most certainly R)
  • other stats languages like matlab and R don’t require much programming knowledge to get started, but harder to dev new tools in them
• michaellindon/distributions
  • open-source clojure lib for generating and working with probability distributions in clojure
  • can also provide data and prior to get posterior distribution
  • and do posterior-predictive distributions
• wrote a way to generate random functions over a set of points (for trying to match noisy non-linear data)
• was easy in clojure, because of lazy evaluation (can treat the function as defined over an infinite vector, and only pull out the values we need, without blowing up)
• …insert lots of math that i couldn’t follow…

• came from a python background for machine learning
• thinks there’s a good intersection between functional programming and machine learning
• will show how to build a baby classification model in clojure
• expert systems: dominant theory for AI through 2010s
  • limitations: sometimes we don’t know the rules, and sometimes we don’t know how to teach a computer the rules (even if we can articulate them)
• can think of the goal of machine learning as being to learn the function F that, when applied to a set of inputs, will produce the correct outputs (labels) for the data
• power of neural nets: assume that they can make accurate approximations for a function of any dimensionality (using simpler pieces)
• goal of neural nets is to learn the right coefficients or weights for each of the factors that affect the final label
• deep learning: a “fat” neural net…basically a series of layers of perceptrons between the input and output
• why clojure? we already have a lot of good tools in other languages for doing machine learning: tensorflow, caffe, theano, torch, deeplearning4j
• functional composition: maps well to neural nets and perceptrons
• also maps well to basically any ML pipeline: data loading, feature extraction, data shuffling, sampling, recursive feedback loop for building the model, etc
• clojure really strong for data processing, which is a large part of each step of the ML pipeline
  • ex: lazy sequences really help when processing batches of data multiple times
  • can also do everything we need with just the built-in data structures
• cortex: meant to be the theano of clojure
  • basically: import everything from it, let it do the heavy lifting
• backend: compute lib executes on both cpu and gpu
• implements as much of neural nets as possible in pure clojure
• meant to be highly transparent and highly customizable
• cortex represents neural nets as DAG, just like tensorflow
  • nodes, edges, buffers, streams
• basically, a map of maps
  • can go in at any time and see exactly what all the parameters are, for everything
• basic steps to building model:
  • load and process data (most time consuming step until you get to tuning the model)
  • define minimal description of the model
  • build full network from that description and train it on the model
• for example: chose a credit card fraud dataset

• director, programmer of his own company
• recommends ccm-clj for cassandra-clojure interaction
• expertise: high-availability streaming systems (for smallish clients)
• systems he builds deal with “inconvenient” sized data for non-apple-sized clients
• has own company: troy west, founded three years ago
• one client: processes billions of emails, logs 10–100 events per email, multiple systems log in different formats, 5K–50K event/s
• 10–100 TB of data
• originally, everything logged on disk for analysis after the fact
• requirements: convert events into meaning, support ad-hoc querying, generate reports, do real-time analysis and alerting, and do it all without falling over at scale or losing uptime
• early observations:
  • each stream is a seq of immutable facts
  • want to index the stream
  • want to keep the original events
  • want idempotent writes
  • just transforming data
• originally reached for java, since that’s the language he’s used to using
• data
  • in-flight: kafka
  • compute over the data: storm (very powerful, might move in the direction of onyx later on)
  • at-rest: cassandra (drives more business to his company than anything else)
• kafka: partitioning really powerful tool for converting one large problem into many smaller problems
• storm: makes it easy to spin up more workers to process individual pieces of your computation
• cassandra: their source of truth
• query planner, query optimizer: services written in clojure, instead of throwing elasticsearch at the problem
• recommends: Designing Data-Intensive Applications, by Martin Kleppmann
• thinks these applications are clojure’s killer app
• core.async gave them fine-grained control of parallelism
• recommends using pipeline-async as add-on tool
• composeable channels are really powerful, lets you set off several parallel ops at once, as they return have another process combine their results and produce another channel
• but: go easy on the hot sauce, gets very tempting to put it everywhere
• instaparse lib critical to handling verification of email addresses
• REPL DEMO
• some numbers: 0 times static types would have saved the day, 27 repos, 2 team members

The Power of Lacinia and Hystrix in Production

• few questions:
  • anyone tried to combine lysinia and hystrix?
  • anyone played with lacinia?
  • anyone used graphql?
  • anyone used hystrix?
• hystrix : circuit-breaker implementation
• lacinia: walmart-labs’ graphql
• why both?
• simple example: ecommerce site, aldo shoes, came to his company wanting to rennovate the whole website
• likes starting his implementations by designing the model/schema
• in this case, products have categories, and categories have parent/child categories, etc
• uses graphvis to write up his model designs
• initial diagram renders it all into a clojure map
• they have a tool called umlaut that they used to write a schema in a single language, then generate via instaparse representations in graphql, or clojure schema, etc
• lacinia resolver: takes a graphql query and returns json result
• lacinia ships with a react application called GraphiQL, that allows you to through the browser explore your db (via live queries, etc)
• gives a lot of power to the front-end when you do this, lets them change their queries on the fly, without having to redo anything on the backend
• problem: the images are huge, 3200x3200 px
• need something smaller to send to users
• add a new param to the schema: image-obj, holds width and height of the image
• leave the old image attribute in place, so don’t break old queries
• can then write new queries on the front-end for the new attribute, fetch only the size of image that you want
• one thing he’s learned from marathon running (and stolen from the navy seals): “embrace the suck.” translation: the situation is bad. deal with it.
• his suck: ran into problem where front-end engineers were sending queries that timed out against the back-end
• root cause: front-end queries hitting backend that used 3rd-party services that took too long and broke
• wrote a tiny latency simulator: added random extra time to round-trip against db
• even with 100ms max, latency diagram showed ~6% of the requests (top-to-bottom) took over 500ms to finish
• now tweak it a bit more: have two dependencies, and one of them has a severe slowdown
• now latency could go up to MINUTES
• initial response: reach for bumping the timeouts
• time for hystrix: introduce a circuit breaker into the system, to protect the system as a whole when an individual piece goes down
• hystrix has an official cloure wrapper (!)
• provides a macro: defcommand, wrap it around functions that will call out to dependencies
• if it detects a long timeout, in the future, it will fail immediately, rather than waiting
• as part of the macro, can also specify a fallback-fn, to be called when the circuit breaker is tripped
• adding that in, the latency diagram is completely different. performance stays fast under much higher load
• failback strategies:
  • fail fast
  • fail silently
  • send static content
  • use cached content
  • use stubbed content: infer the proper response, and send it back
  • chained fallbacks: a little more advanced, like connecting multiple circuit breakers in a row, in case one fails, the other can take over
• hystrix dashboard: displays info on every defcommand you’ve got, tracks health, etc
• seven takeaways
  • MUST embrace change in prod
  • MUST embrace failure: things are going to break, you might as well prepare for it
  • graphql is just part of the equation, if your resolvers get too complex, can introduce hystrix and push the complexity into other service
  • monitor at the function level (via hystrix dashboard)
  • adopt a consumer-driven mindset: the users have the money, don’t leave their money on the table by giving them a bad experience
  • force yourself to think about fallbacks
  • start thinking about the whole product: production issues LOOK to users like production features
• question: do circuit-breakers introduce latency?
  • answer: a little bit at the upper end, once it’s been tripped

• works at magento, lives in philly
• really wants to be sure our future robot masters are written in clojure, not python
• guildsman: tensorflow library for clojure
• tensorflow: ML lib from google, recently got a c api so other languages can call into it
• spoiler alert: don’t get TOO excited. everything’s still a bit of a mess
• but it DOES work, promise
• note on architecture: the python client (from google) has access to a “cheater” api that isn’t part of the open c api. thus, there’s some things it can do that guildsman can’t because the api isn’t there
• also: ye gods, there’s a lot of python in the python client. harder to port everything over to guildsman than he thought
• very recently, tensorflow started shipping with a java layer built on top of a c++ lib (via jni), which itself sits on top of the tensorflow c api, some people have started building on top of that
• but not guildsman: it sits diretly on the c api
• in guildsman: put together a plan, then build it, and execute it
• functions like guildsman/add produce plan maps, instead of executing things themselves
• simple example: adding two numbers: just one line in guildsman
• another simple example: have machine learn to solve | x - 2.0 | by finding the value of x that minimizes it
• tensorflow gives you the tools to find minima/maxima: gradient descent, etc
• gradient gap: guildsman can use either the clojure gradients, or the c++ ones, but not both at once
  • needs help to port the c++ ones over to clojure (please!)
• “python occupies the 9th circle of dependency hell”: been using python lightly for years, and still has problems getting dependencies resolved (took a left turn at the virtual environment, started looking for my oculus rift)
• demo: using mnist dataset, try to learn to recognize handwritten characters

• educator, started using scheme in 1994, picked up clojure in 2009
• origins of lisp: john mccarthy’s paper: recursive functions of symbolic expressions and their computation by machine, part i
• implementation of the ideas of alonzo church, from his book “the calculi of lambda-conversion”
• “you can always tell the lisp programmers, they have pockets full of punch cards with lots of closing parenthses on them”
• steve russel (one of the creators of spaceware) was the first to actually implement the description from mccarthy’s paper
• 1962: lisp 1.5 programmer’s manual, included section on how to define lisp in terms of itself (section 1.6: a universal lisp function)
• alan kay described this definition (of lisp in terms of lisp) as the maxwell equations of software
• how eval and apply work in clojure:
  • eval: send it a quoted list (data structure, which is also lisp), eval will produce the result from evaluating that list
    • ex: (eval '(+ 2 2)) => 4
  • apply: takes a function and a quoted list, applies that function to the list, then returns the result
    • ex: (apply + '(2 2)) => 4
• rules for converting the lisp 1.5 spec to clojure
  • convert all m-expression to s-expressions
  • keep the definitions as close to original as possible
  • drop the use of dotted pairs
  • give all global identifiers a ‘$’ prefix (not really the way clojure says it should be used, but helps the conversion)
  • add whitespace for legibility
• m-expressions vs s-expressions:
  • F[1;2;3] becomes (F 1 2 3)
  • [X < 0 -> -X; T -> X] becomes (COND ((< X 0) (- X)) (T X))
• dotted pairs
  • basically (CONS (QUOTE A) (QUOTE B))
• definitions: $T -> true, $F -> false, $NIL, $cons, $atom, $eq, $null, $car, $cdr, $caar, $cdar, $caddr, $cadar
  • note: anything that cannot be divided is an atom, no relation to clojure atoms
  • last few: various combos of car and cdr for convenience
• elaborate definitions:
  • $cond: own version of cond to keep syntax close to the original
  • $pairlis: accepts three args: two lists, and a list of existing pairs, combines the first two lists pairwise, and combines with the existing paired list
  • $assoc: lets you pull key-value pair out of an association list (list of paired lists)
  • $evcon: takes list of paired conditions and expressions, plus a context, will return the result of the expression for the first condition that evaluates to true
  • $evlist: takes list of expressions, with a condition, and a context, and then evalutes the result of the condition + the expression in a single list
  • $apply
  • $eval
• live code demo

• “the most popular programming language in computer science”
• no compiler, but lots of cross-translations
• would say the name of the language, but doesn’t seem to have one
• so: CSM (computer science metanotation)
• has built-in datatypes, expressions, etc
• it’s beautiful, but it’s getting messed up!
• walk-throughs of examples, how to read it (drawn from recent ACM papers)
• “isn’t it odd that language theorists wanting to talk about types, do it in an untyped language?”
• wrote toy compiler to turn latex expressions of CSM from emacs buffer into prolog code, proved it can run (to do type checking)
• inference rules: Gentzen Notation (notation for “natural deduction”)
• BNF: can trace it all the way back to 4th century BCE, with Panini’s sanskrit grammar
• regexes: took thirty years to settle on a notation (51–81), but basically hasn’t changed since 1981!
• final form of BNF: not set down till 1996, though based on a paper from 1977
• but even then, variants persist and continue to be used (especially in books)
• variants haven’t been a problem, because they common pieces are easy enough to identify and read
• modern BNF in current papers is very similar to classic BNF, but with 2 changes to make it more concise:
  • use single letters instead of meaningful phrases
  • use bar to indicate repetition instead of … or *
• substitution notation: started with Church, has evolved and diversified over time
• current favorite: e[v/x] to represent “replace x with v in e”
• number in live use has continued to increase over time, instead of variants rising and falling (!)
• bigger problem: some sub variants are also being used to mean function/map update, which is a completely different thing
• theory: these changes are being driven by the page limits for computer science journals (all papers must fit within 10 years)
• overline notation (dots and parentheses, used for grouping): can go back to 1484, when chuquet used underline to indicate grouping
  • 1702: leibnitz switched from overlines to parentheses for grouping, to help typesetters publishing his books
• three notations duking it out for 300 years!
• vectors: notation -> goes back to 1813, and jean-robert argand (for graphing complex numbers)
• nested overline notation leads to confusion: how do we know how to expand the expressions that are nested?
• one solution: use an escape from the defaults, when needed, like backtick and tilde notation in clojure
• conclusions:
  • CMS is a completely valid language
  • should be a subject of study
  • has issues, but those can be fixed
  • would like to see a formal theory of the language, along with tooling for developing in it, checking it, etc
  • thinks there are opportunities for expressing parallelism in it

Declarative Deep Learning in Clojure

• starts with explanation of human cognition and memory
• at-your-desk memory vs in-the-hammock memory
• limitation of neural networks: once trained for a task, it can’t be retrained to another without losing the first
  • if you train a NN to recognize cats in photos, you can’t then ask it to analyze a time series
• ART architecture: uses two layers, F1 and F2, the first to handle data that has been seen before, the second to “learn” on data that hasn’t been encountered before
• LSTM-cell processing:
  • what should we forget?
  • what’s new that we care about?
  • what part of our updated state should we pass on?
• dealing with the builder pattern in java: more declarative than sending a set of ordered args to a constructor
• his lib allows keyword args to be passed in to the builder function, don’t have to worry about ordering or anything
• by default, all functions produce a data structure that evaluates to a d4j object
• live demos (but using pre-trained models, no live training, just evaluation)
• what’s left?
  • graphs
  • front end
  • kafka support
  • reinforcement learning

• disclaimer: personal views, not views of employers
• logo: language to control a turtle, with a pen that can be up (no lines) or down (draws lines as it moves)
• …technical difficulties, please stand by…
• live demo of clojure/script version in the browser
• turns out the logo is a lisp (!): function call is always in first position, give it all args, etc
• even scratch is basically lisp-like
• irony: we’re using lisp to teach kids how to program, but then they go off to work in the world of curly braces and semicolons
• clojure-turtle lib: open-source implementation of the logo commands in clojure
• more live demos
• recommends reading seymour papert’s book: “Mindstorms: Children, Computers, and Powerful Ideas”
• think clojure (with the power of clojurescript) is the best learning language
• have a tutorial that introduces the turtle, logo syntax, moving the turtle, etc
• slowly introduces more and more clojure-like syntax, function definitions, etc
• fairly powerful environment: can add own buttons for repeatable steps, can add animations, etc
• everything’s in the browser, so no tools to download, nothing to mess with
• “explaining too early can hurt”: want to start with as few primitives as possible, make the intro slow
• can create your own lessons in markdown files, can just append the url to the markdown file and it’ll load (!)
• prefer that you send in the lessons to them, so they can put them in the lessons index for everyone to benefit
• have even translated the commands over to multiple languages, so you don’t have to learn english before learning programming (!)
• lib: cban, which has translations of clojure core, can be used to offer translations of your lib code into something other than english
• clojurescript repls: Klipse (replaces all clojure code in your page with an interactive repl)
• comments/suggestions/contributions welcome

Stunning. I had no idea of the magnitude of what was lost in Eastern and Central Europe after the War, due to Soviet coercion and control.

By focusing on just the first decade or so after V-E day, and restricting her story to mainly Poland, East Germany, and Hungary, Applebaum is able to go in deep on how the Soviets – and their local communist allies – were able to subvert their newly conquered satellite states, and impose a foreign totalitarian system on them.

Three things I learned:

• Poland, Hungary, Germany, Finland: their borders were radically remade after the Soviet conquest. The Baltic countries vanished altogether, absorbed into the Soviet Union. Germany lost much eastern territory to Poland, who in turn lost its eastern reaches to the Soviet Union. The Ukraine was gone.
• Poland lost 20% of its population in the war. In comparison, France lost 1.5%
• The first step for most of the communist parties was to form a "national front" with other leftist parties, sometimes by force, usually with some amount of arm-twisting. Once that was established, communists would take over the mechanisms of state power (Interior, Secret Police, etc) while leaving the most visible positions in the hands of others, so it looked like a pluralistic government from outside.

Another great meeting! Peter Clines graciously agreed to serve as host, prior to his signing at Mysterious Galaxy (you can order his new book here)

We tried out a slightly different format this time, formally splitting the time between writing craft questions (first half) and publishing/sales questions (second half).

Many thanks to Mysterious Galaxy for the venue, and to Peter Clines for running the show!

My notes:

• Absence of sci-fi thrillers currently, editors starting to mention it
• Character delineation: how to do it? How much is enough? Too much?
• Clines: doesn’t like recommending writing books, because writing is so personal and unique from person to person
• Protagonists need to be: likeable, relateable, and believable
• 3 easy ways to express character: what they say, what they do, and how others react to them
• Indy: when intro side character, will give reader info that the main character doesn’t have, to increase tension
• Plot is what happens outside, story is what happens inside, the character. Every book needs both, the plot to move things along, the story to move us
• Save the Cat: at start of story, main character needs to do something small and simple that lets audience know they’re the person to root for
• Things need to go wrong. We all say the wrong thing sometimes, or have plans go awry, and how we react to that shows a lot of character
• Techniques: one person wrote poems about each of his characters before the book, another wrote backstory for the door her character couldn’t touch, another person puts together portable “murder” boards for her books
• Potato-chip chapters: point is to make each chapter either small enough or end on tasty beat enough to make reader want to go to the next one
• Q: have book that is on the edge of ya and adult, how to market it? Have two versions...
  • A: write it the way you want, submit it the way you want, let editor push for the other if they want it, let them worry about marketing it properly once it’s published
• Q: how to design a book cover?
  • A: hire a book designer, don’t try to do it yourself, if you’re going indy
• Q: do you really sell books on twitter?
  • A: yes, because people tweet that they just bought the book; though took four years of building audience before the book was published
• Social media: different posts for different sites, since the audiences are different between them
• Facebook ads: basically not worth it; check the veritas youtube channel for a good breakdown of how the ads actually perform
• Q: are they going to ask me about how many followers i have on facebook?
  • A: if you have a lot, that’s great, but they care more about how good the book is than anything else
• If you hear about a cool gimmick for your query letter, don’t do it; by the time you’ve heard about it, the gimmick’s played out
• Q: Querying for comics?
  • A: get an artist on board, have the first issue done, and the rest of the arc outlined
• Q: What about hiring an editor?
  • A: nice if you can afford it, may be a good learning experience at first, but not essential to selling a book (just get it in the best shape you can before sending it out)
• A lot of hired editors will start out with just fifty pages, critique that, see if you two want to work together, then continue on with story edits, then finally a copyediting pass

Generally excellent. Where the first book was broad, with multiple locations and times, the second one goes deep, diving into the political minutiae of a single system. And it works, drawing us further into the world of the Radch.

Three things I learned about writing:

• Be careful of "I knew that she suspected I thought I knew about this lie that she told me three days ago" plots. Unless your narrator is very explicit about their thoughts, you can lose the reader in too many significant looks that aren't explained.
• If a cool gimmick from the first book isn't available (lost because of story), instead of bringing it back (and reaching for a retcon), try to find a different way to achieve the same thing. Here, the data relayed to the narrator by Ship gives us the ability to view scenes we wouldn't otherwise, preserving the narrative trick of the first book by a different means.
• For a sequel, you might be tempted to go broader than the first book (especially if the story of the first book was epic in scope already). But you don't have to. A smaller scope can work just as well to let you show who your characters are, and deepen their relationships.

Revelatory, especially when paired with Year Zero. Sebestyen shows how the Cold War began, so soon after the Allies won. Cracks between the Big Three (US, Britain, Soviet Union) that had been papered over for the sake of the war quickly grew into major rifts.

Three of the countless things I learned:

• The Soviet Union didn't steal the entire atomic bomb. Their stolen intelligence helped them move faster, by perhaps two years, but their scientists did the majority of the work themselves.
• Mao financed his armies and kept his population fed during the Chinese Civil War by growing and selling opium (!)
• Japan had been bombed far worse than Germany. Many millions lost their homes. 80% of its merchant shipping fleet was gone. Half of its agricultural land was waste. In the months after the war, Allied survey teams discovered Japan could not have carried on much longer than it did.

Got multiple rejections this week.

One was from an agent I’d queried about representing my novel. That was the fastest rejection I think I’ve ever gotten. I emailed in the query, and 24 hours later I had a rejection in my inbox.

Second one was for a short story I’ve been shopping around. The editor included feedback on what they liked and what they feel the story needs to improve, though, so I’m taking that as a good sign.

Meanwhile, I’m trying to fight off a cold, edit my third short story from this summer, and start editing my second novel. Oh, and now I need to find a new market to send that newly-rejected short story to.

Sometimes I wish I could take a week off the day job just to catch up on everything. Sometimes I feel like I’d need a month.