Let's see how fast I can make $2117.91 USD. The goal is by end of day, Sunday March 18th.

I made it! 🎉

Income to earn: $0.00!
In the bank: $47.00.
Contracted but not yet invoiced: $2100.91.

I am live-blogging my entire process and thought patterns over the three day challenge here. Follow along!

Frequently Asked Questions

Twitter: @richlitt
Email: richard@burntfen.com


- Mon at 00:47 - How did it go?
- Sun at 19:14 - The crash
- Sun at 17:12 - Art
- Sun at 13:02 - Jekyll Scheduler builds on command
- Sun at 10:35 - Goal achieved
- Sun at 02:10 - Express, Heroku, and OAuth conquered
- Sat at 19:23 - At the bleeding edge
- Sat at 16:56 - Getting Probot working
- Sat at 15:54 - Providence at the cafe
- Sat at 15:14 - Business models for Jekyll Scheduling
- Sat at 14:48 - Negative feedback
- Sat at 14:35 - Scheduled Jekyll Posts
- Sat at 09:56 - Morning reflections
- Sat at 00:59 - First day post mortem
- Sat at 00:21 - Better navigation
- Sat at 00:03 - Working blog
- Fri at 22:56 - Setting up a blog
- Fri at 18:06 - Adventure branding
- Fri at 16:03 - Patreon Post
- Fri at 15:36 - Afternoon goals
- Fri at 13:28 - Hunger
- Fri at 13:06 - Marketing this project
- Fri at 12:40 - Machine Learning?
- Fri at 11:54 - Probot
- Fri at 11:42 - First Client!
- Fri at 11:13 - Small notes and Buffer
- Fri at 10:33 - Reputation
- Fri at 10:32 - First Contact
- Fri at 10:19 - The First Tweet
- Fri at 10:12 - Introduction

View the Project on GitHub

This project is maintained by RichardLitt

At the bleeding edge

Ok, the last three hours has been a bit of a whirlwind. I ran into an issue where GitHub actually doesn’t allow you to reset your build yet using the API if you are a bot. This wasn’t documented by GitHub in their API, so I’m at the bleeding edge of what they’re doing. That’s reassuring.

After spending a while trying to hack this by making an empty commit message and pushing that every hour, I’ve realized a few things. First, I shouldn’t be doing this - it’s a way of dirtying up the commit history. Secondly, I should wait a bit. I don’t want to actually add thousands of commits, which is what this would do.

Instead, there’s another solution I should look into: using OAuth permissions. This works, I know, because I’ve done it using curl from my terminal. So, the next step is to actually just get an OAuth app running on Heroku and using that to log permissions and set a scheduler to hit GitHub. I historically have had a lot of difficulty with OAuth, and with storing logs, so I’m a bit worried, but I think that this should be doable fairly easy. It also gives me the added benefit of being able to charge users for scheduling posts by adding a Stripe dashboard on the front end of that app.


Now, it’s dinner time. I am hungry. I am going to take a break, and tackle this after dinner.

On a side note, Ricardo (my friend from this morning) was at the cafe I was working at this afternoon. Good seeing him, and he and Bruno (the other dev from the last post) had some good ideas and enthusiasm. Excited for tonight’s work.

Let’s eat some steak.

Beam me home, Scotty!