"The beginning of wisdom is the definition of terms." - (attributed to) Socrates

I'd argue that for any conversation between people to make progress, they have to have some agreeance on what they're talking about. A counter example, if I were to order a 1/4" bolt from someone and we have different measurement standards of what 1/4" is, I won't be able to build on what I've received from them. Consistency is the key characteristic that allows interoperability between multiple parties.

I appreciate greatly that Gwern uses confidence tags to convey this aspect, as it gives me a relative sense of how much I can trust a piece of evidence.

Maybe most important, I'd also argue that even if standardized usage is only used throughout the AIS community, that would be worthwhile in itself. Living in the Bay and participating in a lot of doom conversations, I believe a lot of nuance is missed and unjustly has people updating priors when having a standardized set of terms would allow people to notice when something seems off about another person's claim.

That said, even if this wouldn't help with informal discussions within the community, having more discrete terms to share would allow for higher quality information transfer between researchers, similar to the 1/4" bolt example above.

Following up on this; do you have these notebooks available?

Possibly of interest: https://arxiv.org/abs/2403.14380

"We found that participants who debated GPT-4 with access to their personal information had 81.7% (p < 0.01; N = 820 unique participants) higher odds of increased agreement with their opponents compared to partici- pants who debated humans. Without personalization, GPT-4 still outperforms humans, but the effect is lower and statistically non-significant (p = 0.31)."

the abuse of doubt

New link

the improper use of humility

New link

I really liked this essay a lot, especially how it shows the importance and necessity of creativity in such a rigorous field like mathematics for being able to explore and potentially end up wrong. This sprung up many thoughts:

• Advice I had heard from Jacob Lagerros, "If you're not embarrassed by what you ship, you ship too late."

  • Contra the first technique the author mentions, having the audacity to put out a bad product seems good for feeling the fear but continuing to work anyways, continuing to explore what's unknown to you.

• The etymology of the words experiment, experience, and finally expert all are based on the root "-per", meaning "to try, to dare, to risk".

  • In "Lean Manufacturing" Eric says "I’ve come to believe that learning is the essential unit of progress for startups." This is in response to putting out features of a product, finding out they don't work but realizing what it is that they got wrong and being able to update accordingly and reorient in the direction that leads to a better product.

• Tip: work so fast you don't have time to self-censor:

  • Writing and editing are two very different processes, and writing as if you're writing the final result will be will stunt you.
  • I often write without spellcheck on, otherwise it stops the flow.

• Quote from another Paul Graham essay "How to Think for Yourself", "To be a successful scientist, for example, it's not enough just to be correct. Your ideas have to be both correct and novel."

  • In your post you mention "being exceptionally talented and trained was, in the long run, not enough to do groundbreaking work because they lacked the capacity to go beyond the context they had been raised in"
  • There's also reminiscing of "definition of sanity is doing the same thing over and over again, expecting different results"; if you don't do something different then you won't get different things.
  • The author mentions "But strangely enough, this fragile margin is where the ideas that make our society possible come from" and I think that doesn't get emphasized enough in most formal schooling I've been a part of; instead of asking what people can bring to the table it's mostly "only make time for what others have done".

• Personal advice on doing projects: Instead of waiting for the perfect opportunity, find a good one, do good and optimize from there (if you're in the state of not being established and aren't sure what to do). (This advice may be wrong, not certain.)

• When writing a more important email I can't draft the response in the email response, I have to write it out in my notes. I type out the shitty, low quality ideas and then am able to see most importantly 1. the full idea, and 2. exactly what it is that doesn't work. If it's not being observed though, I stay with writer's block.

• A note on the EA / Rat culture that I've been a part of; I've seen people move into this community and if they say something that's possibly not true / even moderately disagreeable, people will quip back some sort of "That's not true:" and dominate the conversation for a while. The intention is to update, but I see people instead stop adding to the conversation out of fear of being wrong and chastised.

• I like this twitter thread that aims in a similar direction of this post, and exploring one's own thoughts

• Maybe a more palatable piece of advice comes from "Sailling True North" by James Stavridis mentions "Creativity and innovation can be paralyzed by fear of failure."

  • In this context he's speaking of war (where some of the advice in the post isn't applicable), but being able to not cave into pressure from outside forces but still recognize and allow those pieces of you that very well could be wrong to surface. This is quite delicate, but I'd argue is massively important.

Paul Graham

Link for the curious http://www.paulgraham.com/greatwork.html

I've heard this comment as, "if you're not paying for the product, you are the product."

I've read this book and tried to read it again as I thought I was missing something, but my impression of the book is that it's somewhat sloppy, a bit preachy of ZK being a cure-all, makes much more complicated a very simple system to the point of obfuscating the main point.

To my understanding, all the Zettlekasten is is having notes with:

1. individual names (if you look for one name, one note comes up), 
2. creating links between associated ideas (if you think, "wow, this reminds me of..." you may forget that connection later, so you link them), and 
3. having indexes to point you to good starting points when you develop strings of thoughts / notes.

The indexes are the most complicated part. It's just that you don't file notes under a single folder (as it separates from the ideas that aren't related, but also the ones that are) so instead you semantically connect ideas on an object level basis. In order to get a general sense of the full thought you developed ("when I was researching about x, what were the main conclusions I came to?") you can look at these indexes for a nice directory of your past thoughts.

Appreciate the reply, thank you!