A comprehensive and up-to-date developer education platform for Urbit.
This project organizes developer capabilities into a hierarchy of competencies (“objectives”), competency clusters (“lessons”), and ultimately developer education paths.
Given a particular target capability, we can answer the question of exactly what parts of the system you need to learn to be competent at your task.
More or less, we consider the world of Urbit developers to fall into six levels:
- Tyro
- Amateur
- Workaday
- Master
- Wizard
- Client-side
We organize curriculum into series which describe the target transformation:
- 100 Tyro→Amateur
- 200 Amateur→Workaday
- 300 Workaday→Master
- 400 Master→Wizard
- 500 Wizard++
Particular paths can be traced through the competency cluster dependencies. The point isn't to make this overly complicated, it's to make sure that we know what you need to know to accomplish a particular task.
A competency cluster looks like this:
uuid: 110
layout: node
title: "Syntax, nouns, auras"
tags:
- "%hoon"
prerequisites:
- "100"
postrequisites:
- "112"
- "113"
objectives:
- "Distinguish nouns, cells, and atoms."
- "Apply auras to transform an atom."
- "Identify common Hoon molds, such as cells, lists, and tapes."
- "Annotate Hoon code with comments."
runes:
- "::"
irregular:
- "@"
- "[]"
- "~[]"
- "''"
- """"
key_points: []
assessments: []
comments: ""
content: ""
with some associated content from urbit.org tutorials and docs. What we are aiming for is that each objective have a quantitative measurable outcome; that is, we should be able to definitively say that one can “identify the special role of the $ buc arm in many cores.” The whole chart looks complicated because some things (like how Jael works, 240 and 290) depend on different prerequisites (in this case, some Azimuth background and how moves work).
This charts shows the General Mathemic Inventory (GMI):
WHEN CHANGING NODES, you need to update the map.csv, the node, and any prerequisite or postrequisite changes.