writing

Why I Wrote It: Epic Resume Go!

by

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

Epic Resume Go! is my book on creating a great resume, focusing on a “storytelling” style – making a resume fun to make (as a kind of narrative media) and interesting to readers. It’s origins illustrate just how an idea can develop – in this case, over a decade.

The origins of Epic Resume Go stretch back about twenty years. I was reading some article in a local employment newspaper (think of it as “Dice.com” before the internet was the job search place) about resumes. The article noted that you wanted to make your skills and experience apparent.

That lovely little article kicked off my interest in making good resumes. Over time I polished my method of making resumes, and got good results from them – people liked them. A person interviewing me for a job mentioned I’d covered everything, that I told a good story. That’s when it struck me – I was telling a tale.

It was pretty obvious in retrospect. I had an introduction (setting a scene), skills (showing what I can do), a history (like a backstory), and bits like hobbies that showed me as a person. It showed who I was and where I was going – and that bit of feedback helped me further perfect my method.

As life went on, I found myself giving people advice on resumes. This meant I was learning more, but also I kept giving the same feedback. So why not a book?

Writing the book was pretty easy, since I already had a system, I just had to give it structure. Thus Epic Resume Go! was born – the idea was to make it an exciting title evoking things like Sentai and anime. Because I’m a nerd.

I also paired the book with speaking at cons and developing handouts. This helped people out more – but also it meant I now had several things to send people who needed advice. Sometimes reading my stuff was far more productive than letting me ramble.

I even rewrote the book later, wanting to make it clearer and more up to date. Surprisingly, little changed – mostly you had to sync it with your other social media.

If there’s a lesson to take away from Epic Resume Go! it’s that we probably all have something very useful to share that should be in book form. Maybe for friends, maybe for a limited audience, maybe for the world. So why not go for it?

Steven Savage

Why I Wrote It: Fan To Pro

by

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

Ah, Fan To Pro. My attempts to give people advice on how to use their fandom in their careers. The first book I wrote — and the first book I rewrote.

Let’s ask just how it came to be, so we can share our stories of why we make books.

Fan To Pro didn’t start as a book. Or sort of did.

Fan To Pro’s origins go back to 2005 and 2006. Several friends and I kept discussing just how much talent there was in fandom. We wondered how we could support people, especially those wanting to use that in their careers. Our solutions were simple: we weren’t sure.

For a while, a friend and I considered a book, but we weren’t sure what to do. How do you take “hey, you could do this for a living” and make a book out of it? It went nowhere.

What did happen was we created a blog, now closed, called Fan To Pro (later MuseHack). This got us into blogging about careers and career news and introduced us to a range of similar people.

At the same time, I called upon my nascent coaching skills and began presenting about careers at conventions. I spoke on general career advice and brainstorming, and the act of speaking helped me mine my knowledge. This was around 2007-2009, after over a decade in my career, and I had a lot to share.

I also was always working on improving myself. I’d go to professional meetups, get training, and read books. I got exposed to the world of coaching and career books, and that led to a realization.

Why not share my geeky career advice from my point of view. Take what I’d learned and seen over the years and collate it into a book. I already had plenty of presentations and experience, after all.

This was an important lesson. I hadn’t realized what I knew or what I could share until I’d tried. Sometimes we don’t know what we know until we share it.

All my friends and family were supportive, so I got down and wrote my book. Also, they were kind of surprised it took me that long to realize my skills.

The first Fan To Pro was kind of mediocre. I mean, there was good advice, but it had an awful cover, some odd formatting, and there were a few things I missed. But I did get the book done, and I had a starting point.

There are some things where you have to do something and move on to see where you are.

But I wasn’t done. After a few years, I realized I had learned a lot, and it was time to rewrite the book. I sat down, got a professional artist, and revised the heck out of it.

The results were much better. I’m proud I wrote the first book, but I’m proud of the second book. I improved the style, added more information, shared my lessons, and organized it better. It was a far better book.

It also felt like I’d “gotten it all out.” I had shared more lessons, gone into more depth, and connected better with the audience. The book feels complete

Will I ever rewrite it again? I don’t know. I wrote it at a time in my life where it feels like a “got” the big picture. As my career continues, as I age, as the economy changes, I worry my more recent experiences are less applicable. Bluntly, I’d be afraid to screw it up.

But who knows – I never thought I’d do a book at one point in my life . . .

Steven Savage

Writing And Metaphor

by

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

What’s Your Metaphor for writing?

Returning to fiction with my novel, A Bridge To the Quiet Planet and its upcoming sequel, a School of Many Futures, required me to think about writing a lot. Thinking about writing, how to conceive of it, how to pace it, how to develop it helps you, well, write. A metaphor gives you tools to think in and ways to improve.

For nonfiction I think of it in abstract, visual forms. I’m so used to writing it and have for so long that my metaphors are things I see and feel. Perhaps once I had to use more concrete terms, but time makes things unconscious and automatic, and I don’t remember.

But fiction? That was harder because I’d not thought about – and when I was rethinking my writing methods, I realized I was treating fiction as a “physical” thing.

You’ve heard me talk about “Big Rocks” as pieces of fiction and plot. I’ve discussed Agile and stories, but Agile comes from physical manufacturing and store stocking – it often has “physical” ideas built in. I treated stories and chapters as scenes as boxes containing various events.

Did these limit me? Hell yes, because fiction – and indeed a lot of writing – probably isn’t best thought of in physical metaphors. It’s too limiting, too atomistic, too confining.

Now how did I realize this? Because I was analyzing writing (as I always do) and realized how important editing is, and editing requires a product. You make something then improve it.

Writing fiction is like writing computer code.

Computer code is more a living thing, with components and distinct parts, but it works because all its parts come together. It’s about flows of information and functionality. Best of all, as long as you have it working – no matter how awful – you can improve in. In fact, you often have to make bad code to get good code because you don’t know how it’s going to work until you have something.

Seeing this metaphor, this new metaphor, really helped me get over some of my writing challenges. Thinking about the parts of a fictional story as physical started to fade away. I had a way to see things differently.

My metaphor or metaphors may not be yours. Even my more abstract ways of thinking are my ways, not yours. But a challenge to you, my writing friend, is to find what metaphors help you write. What is a good way to compare writing to something else that helps you?

Maybe you have it. Maybe you don’t. Or maybe you just thought of it and have more to explore . . .

Steven Savage