omino code blog

1. A body of code is never finished
2. The authors have in mind some “next steps”
3. The code implicitly supports these particular next steps, and similar ones
4. The code implicitly hinders wildly different next steps
5. Adoption by users implicitly supports the current state and, depending on apparent paradigm, supports the intended next steps
6. Adoption by users resulting in persistent manifestations of the current state — that is, saved documents — explicitly hinders wildly different next steps
7. Intermittent development may distract from those next steps, but they are still implied by the code (and the current state is required by extant persistent documents)
8. Development by new authors may distract from those next step, but they are still implied by the code (and the current state is required by extant persistent documents)
9. If you accelerate for six months towards the wrong star, it takes 18 months to turn your spaceship around, decelerate, and return to your starting point at a stop. Less if you don’t mind overshooting.

Seems about right.

Compelling charts and graphs omitted.