Brian Gilham

Engineering leader, husband, and father

self-publishing

Finish Your Damn Side Project: Update #1

Last week I announced Finish Your Damn Side Project, a new book I’m self-publishing this summer. The reaction has been nothing short of amazing. I knew people were struggling with shipping their side projects — it’s part of the reason I write the Monday Mailer — but it’s obvious developers are hungry for a resource that goes deeper than a weekly newsletter. I’ve wrapped up planning and outlining the book, so I thought it would be a good time to pause and share what’s happened so far.

Last week I announced Finish Your Damn Side Project, a new book I’m self-publishing this summer. The reaction has been nothing short of amazing. I knew people were struggling with shipping their side projects — it’s part of the reason I write the Monday Mailer — but it’s obvious developers are hungry for a resource that goes deeper than a weekly newsletter.

I’ve wrapped up planning and outlining the book, so I thought it would be a good time to pause and share what’s happened so far.

Research

I’ve wanted to write a book for a long time. But I don’t want to write one just for the sake of writing it. Over the last eight months, I’ve had the opportunity to chat one-on-one with many of the 1,200+ people subscribed to the Monday Mailer. Like me, they see the potential for side projects to improve a developer’s skills and level up their career. But, when I ask about the challenges they’re facing, I hear the same issues over and over again:

  • “I don’t have time.”
  • “I’m feeling burnt out.”
  • “I don’t know how to get motivated.”
  • “I have trouble coming up with ideas.”
  • “I’m not sure how to get started.”
  • “I have trouble maintaining focus.”
  • “I keep procrastinating.”
  • “I think too much, instead of taking action.”
  • “I don’t know how to build an audience.”
  • “I’m not sure how to promote my work.”

I see the same concerns pop up in my conversations with other developers, and on sites like Reddit, Hacker News, Designer News, and more. I don’t claim to be an expert when it comes to this stuff. But I’ve managed to consistently ship side projects, throughout my career, while working full-time. I’ve learned some useful techniques along the way, and I think I can help.

Brainstorming

Once I decided to pursue writing the book, I sat down and started brainstorming potential topics. I opened a new document in Ulysses and added a new bullet point for every idea that popped into my head. No editing, no critique. Just opening the flood gates and letting ideas pour out.

I initially tried to do this in MindNode, but quickly realized it wasn’t the right tool for the job. Using MindNode, I felt tempted to try and organize my ideas prematurely. I don’t know about you but, for me, nothing puts the brakes on brainstorming faster than trying to generate ideas and organize them simultaneously.

This process produced somewhere in the neighborhood of 80 different ideas for topics.

Outlining

I knew I didn’t want to start writing until I had some idea of the overall structure. So, I wrote every possible topic down on a Post-It Note and stuck them to the wall.

It looks like pure madness, I know. But it was a fantastic way to see the big picture and start organizing my ideas into distinct sections. Patterns began to emerge, and I knew, if I couldn’t find a section to slot a topic into, I needed to consider cutting it. In the end, I managed to lose 10–15 bad ideas this way.

Getting Organized

My next step was to fire up Trello and create a new board. On it, I created 12 new columns:

  1. Topics
  2. Outlining
  3. Outline
  4. Writing First Draft
  5. First Draft
  6. Writing Second Draft
  7. Second Draft
  8. Writing Third Draft
  9. Third Draft
  10. Being Edited
  11. Edited
  12. Done

I filled the “Topics” column with a card for every topic that made the cut during the outlining step. As I work, I move each card along the conveyor belt of columns. It might seem like a lot of steps, but it means I’ll never lose track of my progress or what I need to do next.

Writing

On Friday, I started writing in earnest. My goal is to write at least 500 words per day. I’ve already completed a 2,000-word first draft for one of the essays. I know the importance of maintaining a daily habit when it comes to side projects. So, I’ll be working hard to try and stick to my daily word count.


I’m Writing a Book

For a few years now, I’ve had a secret goal: write a book. I’ve always admired people like Wes Bos, Jarrod Drysdale, and Nathan Barry — folks who teach what they know, write, edit, record, and sell their work. Developers, designers, writers, and countless others are in a unique position; they have the means to both create and share, or sell, the things they create. I’ve successfully sold products in the past — everything from an icon set to iOS & tvOS apps — but the idea of self-publishing a book has never gone away.

For a few years now, I’ve had a secret goal: write a book. I’ve always admired people like Wes Bos, Jarrod Drysdale, and Nathan Barry — folks who teach what they know, write, edit, record, and sell their work. Developers, designers, writers, and countless others are in a unique position; they have the means to both create and share, or sell, the things they create. I’ve successfully sold products in the past — everything from an icon set to iOS & tvOS apps — but the idea of self-publishing a book has never gone away.

I’m tired of just thinking about it. I’ve decided that 2017 is the year I’m finally going to do it. I sat down a few weeks ago and started outlining. Today, I’m ready to commit publicly.

My book, Finish Your Damn Side Project, will be available this summer.

Over the course of my career, I’ve become skilled at brainstorming, developing, and shipping side projects. In the last few years I’ve released more than ten apps, written countless blog posts & articles, and spoken at events & meetups on a variety of topics — all while holding down a full-time job that I love. Through it all, I’ve learned habits, concepts, tips, and techniques that I — and many other developers — have used to ship side projects consistently.

I share a lot of that advice & research with the Monday Mailer, my weekly newsletter. But feedback from subscribers, along with my research, shows many developers are hungry for more. I don’t claim to be an expert; I’m just a developer who has seen the power of side projects to improve your skills and level up your career. I think I can help.

I won’t lie; I’m a bit nervous. The book will be the first time I’ve taken on a writing project of this size. But I learned a long time ago that it’s important to start new, scary things before you feel like you’re ready. Because you’re never going to feel truly ready.

I honestly believe you don’t need someone else’s permission to share your passion, build an audience, and publish your work. The Monday Mailer is one part of that philosophy, for me. Finish Your Damn Side Project will be another.

Even if it doesn’t go as well as I hope, I’ll still learn a lot along the way. And isn’t that one of the biggest benefits of working on a side project?

In the weeks and months to come, I’ll be sharing regular updates — both in the newsletter and here on Medium. In my next update, I’ll share some of the steps I’ve taken to plan & outline the book, along with how I’m approaching the first draft. Want to stay in the loop and get a discount when the book launches? Sign up for the Monday Mailer.