Typo in title: prioritize, not priorities.
Here’s Claude’s take on a diagram to make this less confusing.
The diagram did not make things less confusing, and in fact did the opposite. A table would be more practical imo.
10 chat sessions
As in, for each possible config, and each possible channel, run ten times from scratch? For a total of 360 actual sessions? This isn’t clear to me.
Regardless: a small useful falsifiable practical result, with no egregious errors in the parts of the methodology I understand. Upvoted.
Much appreciated!
I’ll:
Correct that typo
Add a section back in to hopefully make it less confusing
Current theme: default
Less Wrong (text)
Less Wrong (link)
Arrow keys: Next/previous image
Escape or click: Hide zoomed image
Space bar: Reset image size & position
Scroll to zoom in/out
(When zoomed in, drag to pan; double-click to close)
Keys shown in yellow (e.g., ]) are accesskeys, and require a browser-specific modifier key (or keys).
]
Keys shown in grey (e.g., ?) do not require any modifier keys.
?
Esc
h
f
a
m
v
c
r
q
t
u
o
,
.
/
s
n
e
;
Enter
[
\
k
i
l
=
-
0
′
1
2
3
4
5
6
7
8
9
→
↓
←
↑
Space
x
z
`
g
Typo in title: prioritize, not priorities.
The diagram did not make things less confusing, and in fact did the opposite. A table would be more practical imo.
As in, for each possible config, and each possible channel, run ten times from scratch? For a total of 360 actual sessions? This isn’t clear to me.
Regardless: a small useful falsifiable practical result, with no egregious errors in the parts of the methodology I understand. Upvoted.
Much appreciated!
I’ll:
Correct that typo
Add a section back in to hopefully make it less confusing