Skip to content

Instantly share code, notes, and snippets.

@essen
Last active August 29, 2015 14:25
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save essen/bf98639c21fb986acb90 to your computer and use it in GitHub Desktop.
Save essen/bf98639c21fb986acb90 to your computer and use it in GitHub Desktop.

You need a schedule, man

Overview

Have three kinds of projects/work:

  • money making (gotta buy bread)

  • first class (generally involves a large number of users and/or me having a lot of fun)

  • second class (satellite and toy projects)

I want to spend time on all projects but have to get a schedule because I’m too busy otherwise. I also don’t want to spend all hours of the day working so I hope having a schedule will help.

I also like helping people for free, on IRC or by email, unfortunately this takes a lot of time away from other things. I unfortunately need to prioritize this as well. I still need to listen to questions, of course, but the answers might be better added to the documentation directly rather than provided to each user individually.

Money making

In an ideal world I could work on open source projects all the time. Some of my projects have a very large impact and are used by tons of companies, unfortunately very few companies contribute back, or they do only as an afterthought, and even less of them contribute back financially. I still have to eat so money making is, it pains me to say, my priority.

The following projects and tasks fall into this category:

  • The Erlanger Playbook

  • Consulting

  • Development contracting

  • Training

  • Sponsorship

  • Billing

Ideas on new ways to make money include:

  • Paid support: rather than answer questions graciously, setup something where people can buy time and/or number of questions and then use that to answer the questions. A simple page with Paypal should suffice, I am not Web Therapy after all.

  • Less blog posts, less questions answered, more content in The Erlanger Playbook.

  • Give priority to sponsors for issues related to security

First class projects

This includes:

  • Cowboy

  • Cowlib

  • Ranch

  • Gun

  • Erlang.mk

They are all related projects and part of a larger vision, therefore they are all on the same level. At different times of the year I might work on one or another more often than others, and some require more work than others. I can only try to balance them equally.

Second class projects

This includes:

  • Website maintenance

  • Bullet

  • Esdl2

  • Everything else

These are not very important so they should not receive a big part of the schedule. Better do them when there’s nothing important left in first class projects.

Schedule

With all this said, I need a schedule. Rather than have a fixed schedule, I need time-based goals per week. I will need to keep track of what I did every week to respect the schedule. For things that take a variable amount of time I need to have minimums and maximums. The more up the list the more priority it gets.

  • Training: 0 to 3 days (rare occurence, takes priority over everything else)

  • Consulting, Development contracting, Sponsorship, Billing: 0 to 3 days (takes priority over first class projects)

  • The Erlanger Playbook: 2 or more days

  • First class projects: 3 or more days, based on tasks and/or tickets to do

  • Second class projects: when everything else is done

Conclusion

I hope this will allow me to focus on what’s important. I suppose I mostly had to write it. I rather live in a world where I can just give away everything I do, but I suppose we are not in the right world for this yet. So this schedule should help me remember and not lose track of this fact.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment