You know how it is

This commit is contained in:
Akko
2025-10-02 20:33:56 +02:00
parent fac0a2266d
commit 0018a7884c
208 changed files with 9923 additions and 887 deletions

View File

@@ -1,5 +1,4 @@
#+TITLE: How this blog is built
#+DATE: <2022-04-18 Mon 14:04>
#+TITLE: How This Blog Works
#+DATE: <2025-09-27 Sat 22:39>
* Blog Tech
** chuu
* How This Blog Works

View File

@@ -1,19 +0,0 @@
#+TITLE: Reserved Jabbing with Pokey Words
#+DATE: <2023-03-16 Thu 18:08>
* Reserved Jabbing with Pokey Words
** Digesting the Writing Advice
I was reading [[https://slatestarcodex.com/2019/07/04/style-guide-not-sounding-like-an-evil-robot/][a little style guide on Slate Star Codex]]. Now truth be told, I generally find this kind of "don't say this, say that instead" style guide somewhat patronizing and quite irritating (more of a testament to my own rebellious spirit than any indictment of any author) and unhelpfully unnuanced (a more practical complaint), and my first instinct was to want to argue this lack of nuance. On the other hand, Scott is a very skilled communicator and an examplar in how being an enormous dork need not be a barrier to popularity, and there is a more helpful general principle hidden in these rules.
The principle here is that while reading (or listening, viewing, ...), people are constantly /predicting/ what will come next. If what they read is what they expect - all good, the reading flows smoothly, and people interpret the text as saying what they already thought it was saying, which is low effort and comfortable. If, on the other hand, they encounter something unexpected, this will stand out, draw their intention, be interpreted as meaningful.
Staying on the level of single words and turns of phrase, in practice what this means is that when you use an unusual word or phrasing instead of a more conventional (to the reader! "normal speech" is audience-relative!) synonym, it will be taken as deliberate and specific; the reader will interpret your choice to use that word as you having searched for the right word to use because the specific meaning matters.
Often, this is not what you want. In scientific discourse, precision is highly valued, and so scientific writing has a house style of using carefully chosen, specific words. In normal everyday prose, however, this amounts to information overload. Even if the length of the text ends up the same, by choosing unexpected "pokey" words, you are preventing the reader from rounding your message off to their own everyday working set of concepts. In effect, you're making your message less compressible for them. Try and do this sparingly! All of this is simply a special case of the commonsense principles of getting to the point and avoiding extraneous detail.
I am fairly sure this is all supposed to be strongly related to the linguistic principle of [[https://en.wikipedia.org/wiki/Markedness][markedness]], but the wikipedia page on markedness is too technical for me to care enough about parsing and I get the impression that "markedness" is a broad multi-dimensional idea of which this post is a specific instance and my perspective on the topic is too superficial to point at the specific thing I am thinking of.
** Further Thoughts
Having arrived at a nice concise principle of communication, let's take a step back and generalize a bit, because I think this idea of the brain as constantly predicting sensory input and responding to surprises is useful and interesting. Specifically, while writing this it called up something I have read about schizophrenia. In a nutshell, schizophrenics commonly experience something what is called "delusions of reference", in which they interpret innocuous things (e.g. newspaper headlines, things said on radio) as having special meaning to them. In some theories of brain function, there is an explanation for this that goes as follows: the brain is constantly predicting upcoming stimuli. In people with schizophrenia, this sometimes goes awry in a way that makes the brain flag something innocuous as deeply surprising. To the schizophrenic person, this feels as though the stimulus in question is somehow deeply meaningful to them personally, presumably in the same way that choosing an unusual "pokey" word instead of a more common synonym feels deliberate and meaningful.
This is all related to the neuroscientific paradigm of /predictive coding/. I am not articulate enough in this to write about it at length and since all I know about this is from SSC articles I have read, I will just link those: I got the bit about schizophrenia from [[https://slatestarcodex.com/2016/09/12/its-bayes-all-the-way-up/][It's Bayes All The Way Up]] and for more in-depth state-of-the-art neuroscience stuff consider Scott's excellent [[https://slatestarcodex.com/2017/09/05/book-review-surfing-uncertainty/][review of Surfing Uncertainty]].

View File

@@ -1,4 +1,4 @@
#+TITLE: The Gospel According to Saint Francis
#+TITLE: A West Coast Gospel
#+DATE: <2023-03-24 Fri 07:31>
* todo title

View File

@@ -1,31 +0,0 @@
#+TITLE: Loot from my Inboxes
#+DATE: <2025-01-22 Wed 16:58>
* Loot from my Inboxes
Enjoy various links and stuff I found working through hundreds of browser tabs and other piles of "I'll deal with it later".
** French Language
*** https://old.reddit.com/r/French/comments/lcpv6o/faqs_look_here_first_before_posting_a_question/
General French learning FAQ
*** https://www.reddit.com/r/French/comments/7nx4mc/happy_new_year_here_is_over_1gb_of_french/
1GB of frogs and bread
** Tech
*** Gentoo Cheat Sheet
https://wiki.gentoo.org/wiki/Gentoo_Cheat_Sheet
** Sex
*** OSSM Sex Machine
https://www.researchanddesire.com/collections
** Websites
*** Guy who goes to Africa and writes cool notes
https://mattlakeman.org
*** Music ripper thing
https://cobalt.tools/
** Software
*** Panoptikon
https://github.com/reasv/panoptikon
*** Futo android keyboard
https://keyboard.futo.org/
** Interesting
*** Cayley Graphs
https://juliapoo.github.io/mathematics/2023/07/15/plotting-cayley-graphs.html
*** Functions are Vectors
https://thenumb.at/Functions-are-Vectors/

View File

@@ -1,13 +0,0 @@
#+TITLE: Ideas for Articles
#+DATE: <2024-10-15 Tue 15:10>
* Ideas for Articles
** Go through every module in Doom Emacs
** Toshokan retrospective
*** different article?: media lists & scoring
** eris retrospective
** crypto retrospective
** various thoughts on AI:
*** slop is good actually
*** what is intelligence
** expand ambitions article

View File

@@ -1,18 +0,0 @@
#+TITLE: Things left to do for this blog
#+DATE: <2024-10-15 Tue 15:08>
* Things left to do for this blog
** Tech
*** TODO style bullet points as arrows
- I mean these
This might conflict with the current system for collapsing sections.
*** TODO fix collapsing sections on mobile
*** TODO system to mark things as ready for publishing or not
And what about the (public) git repo for this blog?
*** TODO system for footnotes
*** TODO caching
right now I think things end up with stale caches all the time (like the sitemap); should be set with headers
*** TODO system for having different "views" of the blog
i.e. one back end, multiple front ends
*** TODO ability to have spoiler tags

View File

@@ -1,4 +0,0 @@
#+TITLE: Emacs Friday I
#+DATE: <2025-01-24 Fri 15:57>
* Emacs Friday I

View File

@@ -1,4 +0,0 @@
#+TITLE:
#+DATE: <2025-06-11 Wed 18:54>
* Removal of Runescape free trade