1,190 karma · joined January 15, 2021
1. put up a whiteboard somewhere
2. observe with some regularity what your routines are right now (non-judgmentally)
3. write them down (descriptively, not prescriptively)
4. update over time
Then you'd get the chance to notice your routines changing.
1. a full-fledged programming language
2. no namespacing (nothing is private)
3. no modern GUI concepts to take into account (no CSS `flex-direction`...)
4. no edit-compile-run cycle
5. people have written extensions for many decades
6. people always write extensions with the possibility in mind that their extensions may be extended
Then you can probably see how it works, with just your imagination!
Of course there's a number of epiphanies that may be needed... Like how the principle "compose many small Unix programs with text as the universal interface" is just like "compose many functions with return values as the universal interface", or that it isn't an editor and more like a terminal (with integrated tmux-like functionality) that you decided to turn into an editor, or that an editor waiting for text entry is just stuck in a `while`-loop of reading the next input character, what even is a shell, what even is a computer, etc etc.
> The mental motion of “I didn’t really parse that paragraph, but sure, whatever, I’ll take the author’s word for it” is, in my introspective experience, absolutely identical to “I didn’t really parse that paragraph because it was bot-generated and didn’t make any sense so I couldn’t possibly have parsed it”, except that in the first case, I assume that the error lies with me rather than the text. This is not a safe assumption in a post-GPT2 world. Instead of “default to humility” (assume that when you don’t understand a passage, the passage is true and you’re just missing something) the ideal mental action in a world full of bots is “default to null” (if you don’t understand a passage, assume you’re in the same epistemic state as if you’d never read it at all.)
https://www.greaterwrong.com/posts/4AHXDwcGab5PhKhHT/humans-...
And there's a makedeb for it! https://mpr.makedeb.org/packages/prismlauncher
https://github.com/linux-surface/linux-surface/wiki/Supporte...
Was some thread on here the other day, where someone said they routinely give Claude many paragraphs specifying what the code should and shouldn't do. Take 20 minutes just to type it up.
Could you guys maybe print it on paper and send it to my physical mailbox, so I can do this ritual with breakfast? :-)
Yes, but once you get the hang of how to learn well from each exercise, it's interesting how the app will seem purpose-built to... slow you down.
You know that exercise where you arrange words into a sentence? I learned a lot better once I stopped looking at those words for cues, and just formed a sentence in my mind and then looked.
At that point, it's a pure waste of time to assemble the sentence and tap through all the UI transitions, I'd rather see the next exercise right away!
But the app doesn't allow me to! I have to pass the minigame first! At the end, it seems 80% of my effort was spent practicing "how to visually hunt for words in a word-cloud".
But is it not then the same thing, because you already "allocated an ID" by naming it? Did you, before coming up with the 4-char hash, often label things outside the vault with the same names as those found in your vault?
In a distributed system it's another matter.
I'm currently using 6 base-40 chars (upcase and lowcase letters, so e.g. "SXJwzQY") that represent an integer Unix time.
The base-40 alphabet is enough that all IDs up until year ~2099 will fit in 6 chars, and it's nicer to type on the phone when you only have to switch between two keyboard modes, the upcase and lowcase but not also the numbers and symbols mode.
Unfixed for years https://gitlab.gnome.org/GNOME/mutter/-/issues/1473
Not sure if it can execute code blocks tho.
And that you don't ever add website bookmarks to the homescreen, because that makes them similar to apps.