One of the most important ways to learn to code is through building projects. With experience people can imagine their own projects and steps required to get there. Tutorial hell is a place that one can get stuck if they are not careful, so we build our apps to be as non-contrived as possible. We begin with our core tech tools and build up our stack by creating new demos and interesting extensions as we go. The path can be optimized depending on the focus of the student.

Work in Progress Matrix

This matrix roughly maps tech tools to demos, which are developed one day at a time and listed below.

Tech ToolBedRSSPoint-of-SaleiSpooge DailyTooterTodo
RSS1 1
VisJS1 2 1
Cryogen 1
Ras Pi 1
Docker 1
Tachyons 2
Preact 1
VideoJS 1
Pleroma 2
PubGate 3


A good effort to keep people engaged in learning to code is "100 days of code" on Twitter, which also helps people connect with others who may be at a similar level of development and build a following of like minded people. Advanced coders and beginners alike participate in 100 DOC so it's possible that they could even land a gig or job thorugh consistent effort recognized. Some of my best performing Tweets have been to that community, although we do not Tweet each day and do not believe that it needs to be 100 serial days or Tweeting so much as 100 days of coding. Tweeting is one mechanism for accountability.

We have a tree of apps that we are incrementally developing still, which will bring a student in a direction that is aligned with their career aspirations. Since we're in the early stages now we do not have the full catalog fleshed out and will write up a plan upon request of a student, and they can participate so that they can also experience the design and specification process.


"Free cheap ideas"

Here is a list of demos that we've built. The ones marked with a star are available only to students and supporters, but are typically discussed on a live stream and released before long. At present there is a sizable backlog and as a thank-you to supporters we are giving them additional lead time. As we catch up it will always be 2 weeks. If there is demand and time for an author to write summaries we may start posting to a blog as well. If there is no link then it means we've yet to post the demo, and some of them do not have source code posted yet.


This funding method is the result of great deliberate. We want to offer value to supporters, but also to make all knowledge available right away. The balance will be ofering finished projects as downloads to supporters early while enough code to build it from scratch is discussed on the stream.

Our minds are partially poisoned by the idea that scavengers will follow and offer their own versions while attempting to discredit our teachers, but this is an old programmed fear from a time before we recognized the justice and protection of God--think about the movie Antitrust where the Open Source guy is killed: where is the justice? That is not a realistic situation.