Hypertext 2: Zettelkasten. https://blog.oddly-influenced.dev/2025/10/30/hypertext-zettelkasten.html

"A Zettelkasten is a particular sort of hypertext document as well as a technique for creating it. My aim in this post is to give you an understanding of a Zettelkasten document – its parts and its whole – and, more importantly, show something of what it’s *like* to work with a Zettelkasten. A Zettelkasten will appeal to some people much more than to others, and I’d like you to be able to predict where you’d fall on that spectrum.”

Surfacing from replies (see context upthread).

I’ve watched the pendulum swing back and forth multiple times in my career between “code reuse ftw!!” and “no dependencies!!” The one thing I can say with confidence is that both those extremes as dogma are ridiculous and costly. It’s all tradeoffs; you can’t escape the part where you think carefully and contextually.

1/ https://hachyderm.io/@inthehands/115237696859291899

I'm devoting time to Ward Cunningham and friends' Federated Wiki. Experimenting with having both a podcast+transcript and a wikified retelling of the same story. I'm very attached to linear narrative, but I think the "Miller columns” of the federated wiki have a lot of potential for blending narrative and linkiness.

https://critical.wiki.oddly-influenced.dev/view/reading-critically/view/royce-1970

This is not exactly going to be a help in pumping out new podcast episodes. Rather the reverse. Enter: guilt. Still: experimenting is fun.

My understanding of the popular understanding of "technical debt" may be out of date. In your experience, when people say that phrase in casual conversation, do they *primarily* mean:

* crappy code that someone ought to fix sometime?

* deferring some useful action because the near-term benefits outweigh the additional cost to doing the action later?

* getting a partial solution out quickly because it will teach you what a better solution would look like, despite that meaning rework?