TBSFotY vo1 - McGuire "Hello, Hello"

 Seanan McGuire's "Hello, Hello" was initially published in the 2015 anthology "Future visions: Original Science Fiction Inspired by Microsoft". The text is helpfully online at Lightspeed.


I don't have very much to say about this piece, to be honest. It's not that it has anything wrong with it, I think it's a perfectly good bit of science fiction, it's more that it doesn't have the same kind of emotional resonance than some of the other pieces in the book so far. 

I do think that it presents domestic very well - I recognize a lot of what's presented as being absolutely true. That's really good stuff.

I do think I learned something from it though - there's a kind of magic to the mystery at the heart of the story (which I can't summarize without spoiling the story). Part of what makes the story interesting is the mystery that needs to be solved - but, something for writers to keep in mind is that a story that relies on this kind of reveal, where does the re-readability come from?

In McGuire's story, I think there's some compelling family dynamics that might be cool to revisit, but I'm less likely to reread it than I am Miller's "Calved" or even Shoemaker's "Today I am Paul" where the personal is, at least in my reading, explored in a much deeper way.

This may be, though, because what we're presented with in these two other stories are families at a crisis point -- whereas the family in "Hello, Hello" is actually pretty well adjusted.

Comments

Post a Comment

Popular posts from this blog

JCE's Gifted and Talented Center

Image
Back in South Africa, in the early 90s, I was invited to take part in programmes offered at the Johannesburg College of Education's "Gifted and Talented Center". I can barely remember much about it. I recall that I did courses in electronics, drama, programming, and study techniques. Further, I remember the buildings and the general feeling of the place (massive buildings, alcoves with chairs and windows in the long passages between primary blocks, etc.). However, I couldn't remember very much around the nature of the programme (if, indeed, I ever knew anything about it) - who funded it, how were pupils identified, etc. I tried searching online but to no avail, there was one hit on someone's personal blog, but that was it. I did, however, manage to find the director of the JCE Gifted Child Enrichment Center from the time I attended and took a chance, asking him if he'd be willing to provide me with some information. He response was both generous and massively
Read more

100 Go Mistakes 10-16

Here we go through the rest of Chapter 2  10 - Not being aware of the possible problems with type embedding Go allows you to not only include types as fields in structs, but also to embed them. Essentially this makes the fields of the embedded/base type part of the "containers" interface. Harsanyi points out that this can lead to exposing more than you might want to, since all of the base type's fields and behaviors are exposed as part of the container. If there is reason to hide the base struct's details, rather simply include it as an unexported field and write accessors. 11 - Not using the functional options pattern I'll admit that I hadn't heard about, or consciously noticed, this pattern before now, but it's quite brilliant. An issue with positional arguments in complex functions is that having tons of arguments that are either null, or unused along certain paths, etc. is a real PITA. My own preference, when factoring out the functionality into mult
Read more

100 Go Mistakes: 1-9

So I'm pretty much looking for a place to write up notes on things I'm reading - which, right now, includes Teiva Harsanyi's "100 Go Mistakes and How to Avoid Them" (does anyone else get confused when writing title-case? Let me look up the rules quick ).   Anyway, I'm at a point where I want to write down some of what I'm learning so I can refer back to it later, so let's go. 1 - Unintended variable shadowing Go's short variable declaration operator (:=) can introduce unintended effects if you're making use of it within nested blocks. Here's a simple example . The workaround is really to explicitly assign the value to the variable declared in the outer scope, either by using temporary variables when using the declaration operator, or simply assigning directly. 2 - Unnecessary nested code This provides a fairly useful heuristic with regards to code complexity. Essentially, Harsanyi wants us to try, as far as possible, to keep the "happ
Read more