Coding vs communicating learning goals

Over the past weeks I've been spending my one or two hours a week refactoring the Learning Goals source-code, removing the shortcuts that I'd taken to get the initial prototype and replacing them with maintainable, well-tested code. But I'm always torn - should I be spending my time instead getting more involved in educational communities, communicating the ideas behind learning goals, drumming up support with Matt's 5 steps? With the time I've got available, it's hard for me to see a sustainable path forward.

But none-the-less, I need to somehow make it easier to demonstrate why learning goals will be a vital tool for flexible learning (with something more concrete than the 1 minute pitch video). So, my plan for the next 6 months (of 1-2hrs per week, so approx. 50hrs):

  1. Finish cleaning up the code (post-prototype-rush) to a point where it's easy for others to contribute (easy dev environment, great test coverage). 10hrs.
  2. Create a simple project sandbox for learning goals on (5hrs)
  3. Build on the site with pages describing the project in 5 sentences, user-stories, surveys of similar projects/products, FAQ etc., so that anyone interested in the project can find all their questions answered, as well as trying out the sandbox. (15hrs)
  4. Give the UI a facelift (well, at least make it styled and mildly attractive, rather then functional-only) (10hrs)
  5. Start a process of releasing new features directly to the sandbox site (automating the process), actively seeking other people/colleges interested in using Learning Goals and continue dogfooding Learning Goals myself with the people whom I'm currently helping.

And as Matt says, shake and repeat.

Comments !