Why I Write

Why I Wrote It – News, Media, and Worldbuilding

by

(This column is posted at www.StevenSavage.com and Steve’s Tumblr. Find out more at my newsletter.)

Why would I do an entire book on news and worldbuilding? Because I was (and am) pissed off at people misunderstanding the importance of news in fiction and life. We’re not talking about my most noble of goals, but it led to a good book.

When I wrote this book in 2019 people were waking up to the impact of disinformation, news-as-propaganda, and internet bullshit. Many people wished this had happened much earlier because plenty of people sounded the alarm, but at least there was an alarm. I was one of the people wishing this had happened a hell of a lot earlier because, look, it is evident that people are tragically deceived between networks like Fox and internet propaganda.

Of course, when I think about real-life issues, I start asking how these issues are portrayed in fiction because it’s what I do.

I realized quickly that fictional settings rarely deal with the questions of how news works. Sure we sometimes get great things like Sir Pratchett’s The Truth, or maybe a reporter character, but I couldn’t recall anything that stood out beyond that. It was time to do two things:

One, keep doing my political activism.

Two, write a damn book on worldbuilding and news.

If that seems petty, it was – I was annoyed and wanted catharsis. However, there were two benevolent motivations:

  • Fiction is a tool to help us understand the world, to think, and imagine. If people who were worldbuilding thought about news, their stories would in turn, make the audience think. Plus, we might get more cool stories out of it.
  • Those reading this book would also think about news and media in general and become more thoughtful. Worldbuilding is very educational, very thought-provoking, and I view it as a form of personal growth.

It was time to write a book on news and worldbuilding – which was also easy.

Remember when I said this age of disinformation got to me? I’ve been a news junkie since I was in my early 20s; I was the guy buying the newspaper in college and turning on 24/7 news on my radio at work. My career in IT has been dependent on information, reporting, and data. You can see why I was annoyed – and that I had a great foundation to write another worldbuilding book.

Yes, some of it felt good to get out.

The result is a pretty good worldbuilding book. It’s got some great questions, some thought-provoking bits, and comes from both the heart and experience. Definitely, one I’d put as high up in my collection because it dealt with something that wasn’t typical to worldbuilding coaching.

It’s also a reminder that a mix of irritation and personal experience is a surprisingly solid start for a book.

Steven Savage

Why I Wrote It: Cities And Worldbuilding

by

(This column is posted at www.StevenSavage.com and Steve’s Tumblr.  Find out more at my newsletter.)

“Cities and Worldbuilding” was my book to coach writers by asking the right questions about their fictional cities. The reason I wrote it, however, is a mix of practical and personal.

First, the practical: Cities are damned complicated things to write.

Many stories take place in cities. Even when they’re not in cities, they’re city-adjacent, or cities are part of the backstory. Cities are everywhere in our imagined worlds – which makes sense because they’re everywhere in our world.

Because they’re so prominent and because we’re used to them, it’s vital to envision them properly. A poorly-imagined city may make a story or game less believable, breaking the tale’s power for us. When an author constructs a city that “feels wrong,” we know because we know cities by sheer familiarity.

When we try to create believable cities, we also find cities are incredibly complex. They take up space, both rely on and change the environment, and grow like living creatures. Cities both require resources and can churn out products and other resources. Finally, they draw upon, rely on, and change people as well – cities are giant social organizations.

I couldn’t avoid writing a book about cities. In fact . . .

There was a personal factor in this as well. That factor is cities fascinate me.

I’ve lived in many cities with long histories, large and small. I’ve watched them grow and change and occasionally make very frustrating construction choices. When I was looking for a job nationally, I visited many cities across America, each different.

Sometimes I like just walking through a city or town and getting a feel for it.

As I’ve provided career advice before, I also kept up on cities and economic choices. That is a soap opera drama all its own, with battles over zoning, public transport, and more. Sure this was important for my job and to help others, but it was also really neat.

Finally, my fiction works in the past, and my current Avenoth series are city-centric. Fantastical cities also interest me as they take all of the above and let you experience cities in new ways. The economics of magic or the culture of an interplanetary crossroads is the kind of thing that gets my attention.

This book was practical and personal, and thus very enjoyable to write. I hope it helps others as well.

Steven Savage

Why I Wrote It: Skill Portability

by

(This column is posted at www.StevenSavage.com and Steve’s Tumblr.  Find out more at my newsletter.)

Skill Portability is an book that comes out of a weird phase of my career writing. It’s a lovely little book, but one I didn’t intend to write until I thought about it.

Many years ago I had an obvious insight on my writing – a good writer keeps writing books. It improves skills, it shares knowledge, and it gets your name out there. As I wrote about careers as well as creativity, I asked myself “what more should I write.”

That’s when I realized that a major part of career advice is transferring skills between one job and another. This is important in general, but moreso for my audiences of fans and geeks – people who want to move their interesting skillset elsewhere. That’d be a great book . . .

. . . because I’d already written it.

Many, many years ago I had written a series of columns on transferring skills between jobs, careers, and even hobbies. I had thought of it as done, but really, sitting on my blog they weren’t doing much (and they’d aged a bit).

But reviving these columns? Expanding them and rewriting them? That had potential for a new book and for helping people even more.

But were they good enough? Well, yes – because I’d already had a system.

The columns themselves outlined a system to analyze how useful skills were – called DARE. It stood for Direct, Advantageous, Representative, or Enhancing – four categories of skills people have. A pile of columns is one thing that may or may not be “bookworkthy” – but one with a system? Something with structure can be built on.

An organized way of thinking about anything, from recipies to job skills, is something that people appreciate. A system allows people to easily understand and employ whatever you’re teaching them. A system also helps one structure something for communicating – like, say a book.

It didn’t take much to turn the columns into a more comprehensive book, and one that’s a nicely useful and light guide.

The real lesson here is that if you think of taking previous writing and expanding it, it helps if it has some organized format to begin with. A system like the above leads to a book. A short story with good structure can be the center of a novel. Structure is a sign you might want to take something farther.

Conversely, if you are writing something or creating something you might think of expanding, consider how it’s organized. Build a system to organize your writing. Put parts of a speech into a clear mnemonic. Something to give it form – because that form can be more easily built on.

Also I’m glad to write up this blog post – because it helps me see the value of the forms I build so automatically. This nice little book wouldn’t have existed without my habitual organization.

Hmmm, maybe another lesson on writing is write on why you write . . .

Steven Savage