Tech — Work — Ramblings

by Mike Kalvas

I see you're not using JavaScript (which is awesome!) on one of my pages that uses it to provide a better experience. If you see something not working right, please let me know. My site should work exactly the same without it apart from any exceptions noted here.

I use prism.min.js to do syntax highlighting. It clocks in at 23kb total in size. Since the majority of the writing I do involves coding, I personally find this to be a worthwhile trade off. If you choose to keep this disabled, rest assured, the code examples are still there, they just may have some extra whitespace and obviously no syntax highlighting.

I do no tracking at all and am a zealot about keeping my pages as small as possible. If you're reading a page of mine that transfers more than about 250kb over the wire (including my most gratuitous indulgence — fonts) I've messed up.

So, if you'd like to have a slightly richer experience, consider enabling javascript for my site and I promise your trust won't be misplaced.

202107292312 Project structure notes should answer a question

Ask a question to start a knowledge project. This could be as simple as focusing your interest to an area worth reading, exploring, and adding to the Zettelkasten. Or this could be something as final as the thesis for an article, essay, paper, blog post etc.

Once you have your question to focus your project, answer it with the standard workflow while making sure to do your thinking inside of the structure note for that project.

Conversely, there are good structure notes that are organizational in nature. They implicitly ask the question "what do we know about this topic?" but they are not "project structure notes" as described here. They aren't about a specific project to learn research, learn, or develop ideas.