Slipstream, part 2.

In my previous post, I talked about how when I was younger, I kept reading science fiction, despite the fact that I often ended up not liking it very much. At this point, people tend to ask me, not necessarily kindly, “Well, what DO you like?”

To really answer that question, I think it’s worth considering some bigger ones: why do you read? What do you expect to get out of the things you read?

For me, the answer to this question is something like this:

In reading nonfiction — and I go through phases where I read a lot of nonfiction — my primary focus is context. Facts are all well and good, but a fact in isolation doesn’t mean much. If it’s a historical event, for instance, I want to know not just what happened, but who was involved, why they made the decisions they made, and what else was happening at the time that affected those choices and their outcome. I may or may not be interested in the author’s opinion or point of view; even if I agree with them, I want to gather enough information to draw my own conclusions.

For me, the pleasure in experiencing non-fiction is in drawing connections. This happened because of this. If not for this event, this one wouldn’t have happened, or wouldn’t have mattered. A connects to B connects to C. If you’ve read my automotive writing, you can see me trying to do this all the time, mostly because I enjoy it. It has the same satisfaction as solving a puzzle.

In reading fiction, I’m looking for a particular tone or feel that fits my mood, or the mood I want to be in. The principal reason I enjoy books I like is that reading them puts me in a headspace that I find pleasurable, cathartic, or evocative. In many respects, it’s like taking different recreational drugs — it’s about applying a filter or lens for my experience and state of mind.

Note that this says nothing about character or plot. I may certainly get caught up in a story because I’m fascinated by a particular character or mystery, but it’s not really the character or the mystery that speaks to me. It’s the way experiencing those characters (or the tension of that mystery) makes me feel.

Let’s consider a recent book that I really enjoyed: William Gibson’s 2007 novel Spook Country. As with many of Gibson’s previous novels, it features a group of disparate characters on separate but ultimately converging quests, tied together by inscrutable conspiracies and hidden agendas. You could, with some justice, call the plot cookie-cutter Gibson. Its cast of characters fall into types familiar from the author’s previous work, and none are particularly likable or sympathetic in any conventional sense. And its resolution is somewhat anti-climatic.

So, why do I enjoy it? For its prose, for one, which is spare, eloquent, and often lovely, and also for its mood. It’s like listening to a song so gorgeous and evocative that you play it over and over again; that you look for other songs like it so you can build a mix that will keep your head in exactly that place for as long as possible. The impact the novel had on me was often in spite of the occasionally banal movements of its plot or its characters. I don’t particularly like the kidnapped junkie Milgrim, for instance, but I like the way Gibson let met share a facet of his perceptions.

As you may gather, what I take from nonfiction is primarily an intellectual satisfaction, while what I take from fiction is mostly an emotional pleasure. The difference between those two poles has a lot to do with why it’s become very hard for me to enjoy science fiction, fantasy, or, for that matter, historical fiction.

Science fiction, fantasy, and historical fiction all share one unfortunate trait in common: the burden of Cumbersome Exposition. Now, any story requires some exposition, and deciding how much and where to put it is one of the biggest challenges for any author. Naturally, if the story is not set in the here and now, the amount of exposition is inevitably greater. Science fiction, fantasy, and historical fiction, however, often suffer an additional problem, which is that the author has done a lot of work on developing the setting (in either invention or research), and he or she is naturally eager to show it off. Sometimes, the author ends up being visibly more interested in the setting than in the characters or story. Even if s/he isn’t, the more exotic the setting, the more work the reader has to do to keep up.

The problem for me is not that I can’t keep up, or even that I don’t enjoy soaking up the minutiae — it’s that it kicks me out of whatever emotional experience I was trying to have (the fiction channel of my brain) into intellectual mode (the nonfiction channel). It throws me out of looking at the work as a story and gets me looking at it as a set of facts to analyze and contextualize. Worse, I might decide the intellectual content is more interesting than the characters and plot. The result is sometimes that I go skipping ahead to the scenes that reveal the backstory, until I’m no longer tracking what’s going on in the plot and don’t particularly care. That can be fun in its own way, but it tends to preclude any kind of satisfactory emotional experience. (When I’m in intellectual mode, also, I’m more likely to be merciless about logical and structural flaws.)

Even with fictional settings with which I’m already very familiar, it’s pretty easy for me to be kicked out of fiction-reading headspace by continuity problems or logical flaws. It’s not that I necessarily care about continuity errors, more that I find them distracting, because it makes me suddenly have to think about the narrative, rather than experiencing it.

My primary criterion for enjoyable fiction, therefore, is a narrative with which I can engage emotionally in a satisfying way, with a minimum of distractions.

Which brings us back to the original question: what DO I like to read?

More on this to follow.

Privacy Preference Center

Privacy and Cookie Preferences

These cookies manage your cookie and privacy preferences. There will typically be several such cookies, each beginning with "gdpr" (e.g., gdpr[allowed_cookies], gdpr&5Bprivacy_bar&5D, and gdpr[consent_types]). They normally expire after about one year. If you delete or disable these cookies, your existing preferences will be lost and you may not be able to save your privacy settings for this website. (These cookies may not be set at all for administrative users unless they access the publicly visible portions of the website.)

gdpr, gdpr[allowed_cookies], gdpr&5Bprivacy_bar&5D, gdpr[consent_types]

Accessibility Settings

If you change certain aspects of the site's appearance using the accessibility sidebar, it may set these cookies to manage and remember your settings. The wahFontColor and wahBgColor cookies, which are set if you alter the site's color scheme, normally expire after about 14 days, but you can remove them immediately by clicking the "Restore Defaults" button on the sidebar.

I may sometimes present an alternative version of the sidebar offering different options, which may set the a11y-desaturated, a11y-high-contrast, and/or a11y-larger-fontsize cookies if you change those settings. These a11y cookies normally expire after about seven days, but are removed immediately if you restore the applicable settings to their default values.

wahFontColor, wahBgColor, a11y-desaturated, a11y-high-contrast, a11y-larger-fontsize

Age Verification

Viewing certain site content may require you to first verify your age by entering your date of birth. If your birth date indicates that you are 18 or older, the website places the age_gate cookie (whose value is "1," meaning "yes, passed") to allow you to access age-restricted content. The cookie remains active for up to 14 days if you click the "Remember me" check box when you enter your birth date; otherwise, the cookie normally expires when you close your browser. If the birth date you entered indicates that you are NOT 18 or older, the website may place the age_gate_failed cookie (whose value is also "1") to prevent you from trying again to access age-restricted content. (The website does not retain your birth date or your age. See the "Age Verification" section of the Privacy Policy for more information about how the age verification system works.)

age_gate, age_gate_failed

Password-Protected Posts

Accessing certain posts or pages on this website may require you to enter a specific password. If you correctly enter the password, the site saves this cookie on your device to allow you access to the password-protected post or page. (For this cookie, "xx" will be a cryptographic hash.) There may be more than one of these cookies, particularly if you access several password-protected posts with different passwords. The cookies normally expire in about 10 days, and are not set at all if you do not access any password-protected content.



When you submit a comment, you may have the option save your information for future comments, storing the info in these cookies. (For each of these cookies, "xx" will be a cryptographic hash.) The cookies are not set at all unless you select that option when submitting a comment. They normally expire in just under one year, but you can delete the cookies in your browser at any time. (These cookies are not usually set for administrative users, since comments they submit while logged in are associated with their user ID number and user profile information rather than a manually entered name and email address.)

comment_author_xx, comment_author_email_xx, comment_author_url_xx

YouTube Videos

These third-party cookies may be set in connection with embedded video players for content hosted on the YouTube video platform (which is owned by Google LLC), for purposes such as (without limitation) managing video settings (such as tailoring the playback to your connection speed), storing video preferences, providing certain functionality such as allowing you to stop and restart a video without losing your place, showing you advertisements, associating your video viewing and other activity with your Google account (if any), ensuring proper functioning of the service, and/or compiling user analytics data. The cookies may be set by various domains, including (though not necessarily limited to),,,,,, and/or (which is part of the DoubleClick advertising service, also owned by Google LLC). Some are session cookies that expire when you close your browser; others may remain on your device as long as your browser settings permit. Some of the cookies that may be set in connection with your Google account and/or advertisements served through the YouTube platform (which may include other cookies not listed here) are persistent cookies that may remain in your browser for as long as your individual browser settings permit. To learn more about what information the YouTube platform and other Google services may collect through and/or in connection with embedded video players and how that information may be used, see the "How Google Uses Information from Sites or Apps That Use Our Services" page and the Google Privacy Policy. For additional information about how Google uses cookies and/or other technologies that may collect and/or process personal information, see the "Technologies" section of the "Google Privacy & Terms" pages. For more information about Google advertising, see the "Advertising" section of the "Google Privacy & Terms" pages, which also discusses the use of cookies by Google advertising services. (Google, DoubleClick, YouTube, and other related marks and logos are trademarks of Google LLC.)

yt.innertube::nextId, yt.innertube::requests, yt-remote-cast-installed, yt-remote-connected-devices, yt-remote-device-id, yt-remote-fast-check-period, yt-remote-session-app, yt-remote-session-name, recently_watched_video_id_list, use_hotbox, demographics, GPS, LOGIN_INFO, PREF, VISITOR_INFO1_LIVE, YSC, AID, ANID, APISID, CONSENT, DSID, FLC, GAPS, IDE, NID, HSID, OTZ, SID, SNID, SIDCC, TAID, exchange_uid, 1P_JAR

Vimeo Videos

These third-party cookies may be set in connection with embedded video players for content hosted on the Vimeo video platform, for purposes such as (without limitation) managing video settings, storing video preferences, providing certain functionality (such as allowing you to pause a video at a particular point), associating your video viewing and other activity with your Vimeo account (if you have one), showing you advertising, and/or compiling user analytics data. The cookies whose names begin with "_ga" and "_ut" are associated with the Google Analytics service (see the "Information for Visitors of Sites and Apps Using Google Analytics" section of the Google Analytics "Safeguarding your data" help page, the "How Google Uses Information from Sites or Apps That Use Our Services" page, and the Google Privacy Policy for more information about how data gathered by this service may be used; the "Google Analytics Cookie Usage on Websites" page provides additional technical information about the cookies the analytics service may use). Cookies whose names begin with "_ceg" are associated with the Crazy Egg web analytics service (which is subject to the Crazy Egg Privacy Policy and Cookie Policy). Cookies whose names begin with "optimizely" are associated with the Optimizely digital experience platform (which is subject to the Optimizely Privacy Policy; the "Privacy" section of the Optimizely Trust Center provides additional information about Optimizely privacy practices, including a link to the Data Processing Agreement offered to customers on whose behalf the Optimizely services process personal data, while the "Cookies and localStorage in the Optimizely snippet" help page provides additional technical information about the cookies and/or similar technologies used by that platform). Cookies whose names begin with "adsense" or that are listed in all caps are associated with the Google AdSense advertising service and/or other Google advertising services (which are also subject to the Google Privacy Policy; for more information about Google advertising services, see the "How Google Uses Information from Sites or Apps That Use Our Services" page and the "Advertising" section of the "Google Privacy & Terms" pages, which also discusses the use of cookies by Google advertising services). The Vimeo Cookie Policy does not currently disclose the normal durations of the cookies and similar technologies that platform uses, but it appears that some may persist for as long as your individual browser settings permit; some cookies set by the Google Analytics service can persist for up to two years. To learn more about what information the Vimeo platform collects and how that information may be used, see the Vimeo Privacy Policy. The Vimeo Cookie Policy also provides information about how Vimeo users can control the use of third-party analytics and/or advertising cookies in connection with embedded Vimeo video players. (Vimeo and the Vimeo logos are trademarks of, Inc., registered in the U.S. and other countries. Google, AdSense, Google AdSense, Google Analytics, and other related marks are trademarks of Google LLC. Crazy Egg is a trademark of Crazy Egg, Inc. Optimizely is a registered trademark of Optimizely, Inc.)

_abexps, aka_debug, clips, continuous_play_v3, embed_preferences, has_logged_in, is_logged_in, jsessionID, player, search_click_position, Searchtoken, stats_end_date, stats_start_date, sst_aid, uid, v6f, vimeo, vuid, _ga, _gads, _utma, _utmb, _utmc, _utmv, _utmz,_ceg.s, _ceg.u, optimizelyBuckets, optimizelyEndUserId, optimizelySegments, adsense, adsenseReferralSourceId, adsenseReferralSubId, adsenseReferralUrl, adsenseReferralUrlQuery, S_adsense, APISID, GAPS, HSID, NID, N_T, PREF, SAPISID, SID, SNID, SSID

PayPal® Buttons

The payment or donation buttons that may appear on portions of the administrative dashboard (which is not normally accessible except to logged-in administrative users) contain embedded content served by PayPal® services. Those buttons may set the third-party cookies PYPF (via, which is owned by PayPal), which appears to check whether or not you are a logged-in PayPal user and is probably used to facilitate the PayPal user login process, and/or 01A1 (via, which is owned by Akamai Technologies), which stores certain technical information about your device and browser, possibly to facilitate the login and shopping cart functions. The PYPF cookie normally expires in approximately four weeks, the 01A1 cookie in approximately one year.

If you use the buttons to make a payment or donation, the PayPal services will set additional cookies (not listed here) to manage your PayPal login and transaction data (and potentially also for various other purposes, such as user analytics and/or advertising). For more information about what data PayPal services collect and how that data may be used, visit the "Legal Agreements for PayPal Services" page to review the PayPal Privacy Statement and Statement on Cookies and Tracking Technologies that apply in your location (the Statement on Cookies and Tracking Technologies that applies to each region is linked from within the applicable PayPal Privacy Statement). For more information about how Akamai may collect, process, and/or use personal data, visit the Akamai "Privacy and Policies" page and Privacy Trust Center. (, PayPal, and all logos related to the PayPal services are either trademarks or registered trademarks of PayPal, Inc. or its licensors. In addition, all page headers, custom graphics, button icons, and scripts related to the PayPal services are service marks, trademarks, and/or trade dress of PayPal. Akamai is a registered trademark or service mark of Akamai Technologies, Inc. in the United States (Reg. U.S. Pat. & Tm. Off.).)

PYPF, 01A1

Administrative and Login Cookies

These functionality cookies are used to manage user logins and other WordPress administrative functions, such as post editing. If you are not an administrative user, they shouldn't normally be placed on your device at all unless you somehow access the login area, which is off-limits to non-administrators.

Accessing the login page places the wordpress_test_cookie (a session cookie that tests whether your browser will allow the cookies needed to log in and expires when you close your browser) and the itsec-hb-login-xx cookie (which expires after about one hour and helps protect the site against "brute force" attempts to hack user passwords). In certain cases, more than one of either or both of these cookies may be set.

Logging in sets the wordpress_logged_in_xx, wordpress_sec_xx, and/or wordpress_xx cookies, which store your user login credentials to allow access to the administrative dashboard and other administrative functions; there may be multiple iterations of each cookie. These cookies expire in about 15 days if you click "Remember Me" when logging in, but if you don't, they normally expire when you close your browser (or, failing that, within about two days). The wp-settings-UID cookies store a logged-in user's configuration settings, while the wp-settings-time-UID cookies store the time those configuration settings were set; again, there may be multiple iterations of each of these cookies, which normally expire after about one year. One or more wp-saving-post cookies may be placed while creating and/or editing posts or pages, to help manage version control and the autosave feature; these cookies normally expire after about 24 hours. The wp-donottrack_feed cookie, which controls a blog feed, may be set by accessing the dashboard menu for the WP DoNotTrack plugin (if we currently have that plugin enabled); this cookie normally expires in about one year.

For all of these administrative and login cookies, the "xx" will be a cryptographic hash while "UID" will be the administrative user's user ID number in this website's WordPress database. (WordPress is a registered trademark of the WordPress Foundation in the United States and other countries.)

wordpress_test_cookie, itsec-hb-login-xx, wordpress_sec_xx, wordpress_logged_in_xx, wordpress_xx, wp-settings-UID, wp-settings-time-UID, wp-saving-post, wp-donottrack_feed

Change Font Size
Change Background Color (Note: This option sets cookies on your device to manage your color settings; see the Cookie Notice for details.)