DRAFT
If I don’t send in a proposal, nothing will happen! I should share my journey, and what my talk will be about.
Call for papers/talks/workshops:
Literature review.
Time for doing.
Key ideas.
Talk outline. Note: I expect that I’ll need to cut scope to stick to 20 minutes, but I think I’ll keep the rough 3 part outline.
Intended talk outcomes.
In May 2022, I decided that I wanted to build my own playful place on the internet. https://play.teod.eu/ was born. I wanted to trust my own choices completely, and make every decision according to my own sense of aesthetics. My previous web site had collapsed under its own weight, and could no longer build, becase of breaking changes in some packages that I used.
I had previously gotten interested in the personal knowledge management movement, primarily Roam Research. I wanted the best parts of Roam with publishing to the web. But I wanted total control. For a time, I explored exporting from Roam to HTML. But I quickly realized that while I loved using Roam’s outlining, it didn’t give me the control I wanted for the web.
A year ago, this effort felt like madness. Today, I feel like it’s one of the better decisions I’ve made in my life. Counted today, I’ve got 12900 lines of org-mode content:
$ cd ~/dev/teodorlu/play.teod.eu
$ find . -iname '*.org' | xargs cat | wc -l
12900
In comparison, my last site got less content:
$ cd ../teodorheggelund.com
$ find . -iname '*.org' | xargs cat | wc -l
1476
I sometimes quote stuff from others, and sometimes copy things around. But I’d guess about 80 % of it is words I’ve written. So something has worked out.
I want to:
applied curiosity: my motivation for writing.
charity, grace and joy: sharing my work with others, and how that’s going.
Other people are curious too! But the world is filled with too much information, so why should you add any more? And how should you share your work with others? My best bet per 2023-04-22: structure your work as narrow theories. In Clojure, we have a culture for writing narrow libraries. A narrow library solves one thing well with minimal dependencies, and minimal impact on your code. I want to argue that the same goes for knowledge. A good article presents and
TODO
copy-pasted things from other places
From Teodor’s public-personal journal, 2023-04-22
Done!
Q: what’s the right interface for making microtheories?
Q: what’s the right interface for making knowledge playlists?
Microtheories need to be good explanations. Examples of good explanations:
a “little memex” is your own corner of knowledge. you curate the index. you create and link your nodes. you can refer to and build on other memexes, but the act building the memex is the reward in itself.
microtheories deserve its own URL. others should be able to leverage your little memex.
a microtheory is a bite-sided deinfition, and motivation for why it matters.
a knowledge playlist is an ordered list of microtheories.
Go!
yes!