The End is Near

Novel edits are coming along faster than I thought. Might actually get them all done by the end of the month 🙂

It’s weird to see the novel being reshaped under my editing scalpel. I can feel the book getting better, little by little: its characters more consistent, the world more fully realized, the pacing tighter.

I’m remembering my plans for a follow-on book, and looking forward to writing it. Can editing a novel make you excited to write the sequel?

The Historian by Elizabeth Kostova

Masterful. Incredibly well-crafted series of nested narratives that simultaneously did a deep dive into Dracula lore and sucked me into a single family’s generations-long saga. Just…wow. So well done.

Three things I learned about writing:

  • You can use flashbacks to cover over narrative time that would otherwise be boring, like train (or plane) travel
  • To make an old myth feel fresh, look for the side that’s not usually given a starring role (like the Turkish side of the Dracula legend), and explore it.
  • Journals and letters are a great way to both nest stories, and keep each story personal, told by the person that lived it

The Shambling Guide to New York City by Mur Lafferty

It’s got an elderly kick-ass demon-assassin, zombies that can think, and a death goddess working at a small press. For that, I can forgive the continuity errors and the occasional odd plot point.

Three things I learned about writing:

  • Watch out for the vague “some”: “something made her”, “something told her”, “some sort of sense”…it gets overused too easily.
  • Where you start your story affects how sympathetic your protagonist seems. Start it when they’re under stress, and readers automatically feel for them. Start it with them relaxed but complaining about how rough they’ve got it, and readers might not be as charmed.
  • Vivid, brief descriptions and snappy dialog can pull a reader through the roughest parts of your story.

Strangely Beautiful, Vol 1 by Leanna Renee Hieber

Gothic” in the overwrought, melodramatic sense.

There’s some fantastic ideas in here, but it was tough one for me to finish.

Three things I learned about writing:

  • People falling love notice everything about their beloved. If writing from the POV of a character falling in love, their thoughts will dwell on even insignificant details about their beloved.
  • Constant repetition of unexplained magical elements makes them annoying and boring. Conserve the magic, to make it interesting.
  • Use a deep dive into a character’s thoughts during conversation sparingly. Dialog should speed the story along, interrupting the flow with paragraphs of thought undercuts momentum and frustrates readers.

Cranking Through

Managed to whittle the list of editing passes from twelve to twenty and now back to thirteen.

Which means I didn’t finish them by the end of March, like I wanted.

I *did* finish the biggest of the changes, though: giving each chapter to either the male or the female protagonist, swapping evenly between the two, and filling out her narrative arc so that her storyline has equal weight.

The changes I have left are much smaller: revising character appearances, adding touches to scene descriptions, and making sure everything is consistent.

Still, I’m setting weekly goals, aiming for three editing passes done each week. At that rate, I’ll be finished with the edits in early May :/

Much later than I’d like, but I tell myself that’s better than not doing them, or worse yet, continuing to tweak and edit for a year or more.

Seven More Languages in Seven Weeks: Julia

Julia feels…rough.

There are parts I absolutely love, like the strong typing, the baked-in matrix operations, and the support for multi-type dispatch.

Then there’s the pieces that seem incomplete. Like the documentation, which is very extensive, but proved useless when trying to find out the proper way to build dictionaries in the latest version. Or the package system, which will install things right into a running repl (cool!) but does it without getting your permission for all its dependencies (boo).

All in all, I’d like to build something more extensive in Julia. Preferably something ML-related, that I might normally build in Python.

Day One

  • can install with brew
  • book written for 0.3, newest version is 0.5
  • has a repl built in 🙂
  • typeof for types
  • “” for strings, ” only for single-chars
  • // when you want to divide and leave it divided (no float, keep the fraction)
  • has symbols
  • arrays are typed, but can contain more than one type (will switch from char to any, for example)
  • commas are required for lists, arrays, etc (boo)
  • tuples: fixed sized bags of values, typed according to what they hold
  • arrays carry around their dimensionality (will be important for matrix-type ops later on)
  • has dictionaries as well
  • hmm: typeof({:foo => 5}) -> vector syntax is discontinued
  • Dicts have to be explicitly built now: Dict(:foo => 5) is the equivalent
  • XOR operator with $
  • bits to see the binary of a value
  • can assign to multiple variables at once with commas (like python)
  • trying to access an undefined key in a dict throws an error
  • in can check membership of arrays or iterators, but not dictionaries
  • but: can check for key and value in dict using in + pair of key, value: in(:a => 1, explicit)
  • book’s syntax of using tuple for the search is incorrect
  • julia docs are really…not helpful :/
  • book’s syntax for set construction is also wrong
  • nothing in the online docs to correct it
  • (of course, nothing in the online docs to correct my Dict construction syntax, either)
  • can construct Set with: Set([1, 2, 3])
  • arrays are typed (Any for multiple types)
  • array indexes start at 1, not 0 (!) [follows math here]
  • array slices include the ending index
  • can mutate index by assigning to existing index, but assigning to non-existing index doesn’t append to the array, throws error
  • array notation is row, column
  • * will do matrix multiplication (means # of rows of first has to match # of columns of second)
  • regular element-wise multiplication needs .*
  • need a transpose? just add ‘
  • very much like linear algebra; baked-in
  • dictionaries are typed, will throw error if you try to add key/value to them that doesn’t match the types it was created with
  • BUT: can merge a dict with a dict with different types, creates a new dict with Any to hold the differing types (keys or values)

Day Two

  • if..elseif…end
  • if check has to be a boolean; won’t coerce strings, non-boolean values to booleans (nice)
  • reference vars inside of strings with $ prefix: println(“$a”)
  • has user-defined types
  • can add type constraints to user-defined type fields
  • automatically gets constructor fn with the same name as the type and arguments, one per field
  • subtype only one level
  • abstract types are just ways to group other types
  • no more super(), use supertype() -> suggested by compiler error message, which is nice
  • functions return value of last expression
  • … to get a collection of args
  • +(1, 2) -> yields 3, operators can be used as prefix functions
  • … will expand collection into arguments for a function
  • will dispatch function calls based on the types of all the arguments
  • type on pg 208: int() doesn’t exist, it’s Int()
  • WARNING: Base.ASCIIString is deprecated, use String instead.
  • no need to extend protocols or objects, classes, etc to add new functions for dispatching on core types: can just define the new functions, wherever you like, julia will dispatch appropriately
  • avoids problem with clojure defmulti’s, where you have to bring in the parent lib all the time
  • julia has erlang-like processes and message-passing to handle concurrency
  • WARNING: remotecall(id::Integer,f::Function,args…) is deprecated, use remotecall(f,id::Integer,args…) instead.
  • (remotecall arg order has changed)
  • randbool -> NOPE, try rand(Bool)
  • looks like there’s some overhead in using processes for the first time; pflip_coins times are double the non-parallel version at first, then are reliably twice as fast
  • julia founders answered the interview questions as one voice, with no distinction between them
  • whole section in the julia manual for parallel computing

Day Three

  • macros are based off of lisp’s (!)
  • quote with :
  • names fn no longer exists (for the Expr type, just fine for the Module type)
  • use fieldnames instead
  • unquote -> $
  • invoke macro with @ followed by the args
  • Pkg.add() will fetch directly into a running repl
  • hmm…installs homebrew without checking if it’s on your system already, or if you have it somewhere else
  • also doesn’t *ask* if it’s ok to install homebrew
  • not cool, julia, not cool
  • even then, not all dependencies installed at the time…still needed QuartzIO to display an image
  • view not defined
  • ImageView.view -> deprecated
  • imgshow does nothing
  • docs don’t help
  • hmm…restarting repl seems to have fixed it…window is hidden behind others
  • img no longer has data attribute, is just the pixels now
  • rounding errors means pixels != pixels2
  • ifloor -> floor(Int64, val) now
  • works!

I Am Providence by Nick Mamatas

Disturbing. Most of the characters are completely unlikable, especially the men: the worst are outright misogynists and racists, even the best act like superior assholes to everyone else.

Mamatas doesn’t pull any punches in exposing the sexism and harassment that happens at fan conventions. It makes for tough reading, both because the female protagonist is constantly experiencing it and because the male narrator, whose death she’s investigating, is one of the superior assholes it’s hard to sympathize with.

Worth reading, though, if nothing else than as a “Do I act like this?” check.

Three things it taught me about writing:

  • – Can get away with very skimpy descriptions — or none at all — if you choose the proper perspective to tell the story from (in this case, a corpse’s).
  • Protagonist’s motivation for pursuing the mystery can be thin, if the reader’s interest is piqued enough for them to want to see it solved
  • Characters will always rationalize their behavior. Even when dead.