gglitch

Nothing will ever ruin email. A private email server, or a federation of mutually-whitelisting ones, is the ultimate social media, and not at all a bad personal information management system too.

Edit: typo

I frequently tell Claude to use "simple, concrete language and uncomplicated syntax, and avoid project jargon, coinages, and abstractions as much as possible," to good effect.

Awesome observation. What would you consider denser?

Wallace was a masterful writer of short fiction, and I think IJ is best read as a (very) long series of short pieces with much that interrelates them.

Past a certain point on my first successful read through, maybe ~300 pgs in, I started realizing that, with very few exceptions, the more abstruse, boring, or frustrating the vignette, the more powerfully it ended; and at that point, I couldn’t put it down. So, in my opinion, skipping around would not make it more fulfilling, and would certainly not make it make more sense (and I do think it would be easy to understate how much they do compose together into a functioning plot for the novel). I could only advocate cultivating an appreciation of the individual vignettes themselves as more-or-less complete short stories.

I’ve been using CC as my GTD-buddy. All the usual plaintext files in a git repo, all the usual processes and workflows and constraints; but I’ve written two skills that have taken the activation energy out of what used to be the hard parts for me: /process-inbox and /weekly-review. Process-inbox interviews me item by item, making suggestions which I accept or amend, and it does the bookkeeping. I tell it when I want to do something and what calendar I want it on and it makes the calendar event. Weekly-review walks through an overview of everything done that week, all my open tasks and projects, makes sure everything has a scheduled next action. Sometimes I make a note, cancel something, reschedule something, whatever.

This is nothing I couldn’t do on my own, and in fact, it’s a lot slower than just manually editing files myself. But: this way it’s actually getting done :)

There’s too much hyperbole on this subject, so I won’t add to it; but it has solved a lot of very-long-running problems of mine.

There's a community and play-style called OSR or "old school renaissance," that recreates versions of the earliest editions of D&D, and encourage a style of play that's heavily oriented around few rules and the DM making quick decisions/rulings on the spot, rather than lots of rules and lots of time spent mining the rulebooks. In fact, the expression is "rulings over rules." This might appeal to you.

I’m using Jekyll for includes and so I can use Ruby to render pages from yaml data. I’m sure Pandoc can do this too one way or another but it’s dead simple out of the box in Jekyll.

I mean, it’s tempting though.

Ion Dunes is outstanding. Very nice work. I would be happy to hear more, and would very much enjoy a writeup too.

Upvoted because it’s a thoughtful question, but honestly I think it’s just that this book and many others like it are addressed primarily to people who are going to use tools like SuperCollider or CSound or raw dsp to create their own entirely original technology stacks for creative work, and an understanding of the physics/math of sound is pretty key to that kind of work, regardless of the musicality of their later creative production.

Might just be a question of taste or personal predisposition. I’m only in Obsidian for the canvas, and I spend almost all my time in it. It’s extremely helpful for me to be able to put all of my buckets up in front of me at once, resize them, rearrange them, color-code them.