Dog-Fooding as a Roadmap
Tags: brainstorming, projects
Published: 2020-04-29 16:05:08

---
title: Dog-Fooding as a Roadmap
published: true
description: Using your own side-project as a user has some incredible benefits.
tags: brainstorming, projects
canonical_url: https://www.assertnotmagic.com/2020/04/29/dogfooding-as-a-roadmap/
cover_image: https://dev-to-uploads.s3.amazonaws.com/i/ylnwgyd48r682eadzrqc.png
---

Tell me if this is a problem you have too: you’re busy.  You love coding as a hobby and working on your side projects when you can steal some time, but those times may be days apart, and you’ve got a lot on your mind.  

It gets to the point where it takes 15 or 30 minutes for you to ramp back into a project and remember where you left off, which means that the window you need to have to actually be productive on your projects grows to closer to an hour.  Obviously, you have less *whole hour* time slots available in your day, so you work on your project less.  This means your project days are even *further* apart, which makes it harder for you to remember where you were at before, and this cycle churns until all you do is dream about what you would do on your project when you’re busy and scroll on your phone in those 15-30 minute time slots you used to be so productive in.

And nothing gets done.

Not just me?  That’s what I thought.  But I had a realization that has been a huge help with this.

## Dog-fooding provides free, passive, effortless inspiration.

What is dog-fooding?  It’s a shortening of the phrase “eating your own dog food,” which means “to use your own product in a real way to put you in the shoes of a user.”

Start using your project in whatever use case you’ve imagined it in.  You will immediately trip over *gobs* of bugs, trouble spots, and unexpected behaviors.  You’ll be amazed at how quickly you go from “Hmm, what was I going to do next with this project?” to “I need to write these ideas down right now before I forget any of them.  There are so many things I need to do!”

## My Use Case: Inkblot

I’m working on making my own static site generator called Inkblot.  Not because there are a shortage of static site generators.  Not because I think I could make a much better one than those out there.  And not because I’m not happy with Jekyll (I love Jekyll).  But because none of them do *exactly* what I want, and because I have an irrational love for markup languages and tools like Markdown, AsciiDoc, Pandoc, YAML, etc. and working on things that have clever ways of turning information in those formats into really cool other things makes me happy.

I also have a 1-year-old baby.  Which means my free-time is scattered, often into time periods where I am exhausted, and my capacity to remember much outside of family and work things has essentially disintegrated.

I got to a point where I thought, “I’m pretty happy with where this project is.  I think it works pretty well!  I’m not really sure what to do next.  There’s probably not much more *to* do!”

*Narrator: It doesn’t.  There is.*

Then I got this idea to start porting my Jekyll site over to Inkblot, and I dropped my 112 (!!!) blog posts into a directory and ran `inkblot build`.

![Older woman typing innocently at a computer as it super error explodes.](https://media.giphy.com/media/EFXGvbDPhLoWs/giphy.gif)

I’ve got some work to do, and my terminal is telling me exactly where to start.  Hopefully this helps you too!