Coding things I may want to pursue, and progress on each.
See also Open source WIP which is “narrower”, less vague.
Idea:
I believe these reasons fit well together.
If I should start coding and have someone “join”, there should be an explicit goal. Or a list of options from which we can select a goal.
This document answers that need.
Progress: none
https://github.com/teodorlu/teodor-notes/
Progress: some design notes in repo README.
Progress: started, long way to finish.
https://www.meetup.com/clojure-oslo/
Idea:
pandocjson2hiccup
togetherGoal: babashka script
Well-defined task, should be possible to do something practical in 30 minutes.
I have previous “systems” for “keeping track of unknown unknowns”. See Open problems. I now believe that list of problems was too wide. Not practical. I think sticking to code might be a narrower, better problem statement.
My other new page Open source WIP bears resemblemnce.