This is a special post for quick takes by Raemon. Only they can create top-level comments. Comments here also appear on the Quick Takes page and All Posts page.
This is an experiment in short-form content on LW2.0. I'll be using the comment section of this post as a repository of short, sometimes-half-baked posts that either:
don't feel ready to be written up as a full post
I think the process of writing them up might make them worse (i.e. longer than they need to be)
I ask people not to create top-level comments here, but feel free to reply to comments like you would a FB post.
Motif coming up for me: a lot of skill ceilings are much higher than you might think, and worth investing in.
Some skills that you can be way better at:
Listening to people, and hearing what they're actually trying to say, and gaining value from it
Noticing subtle things that are important. You can learn to notice like 5 different things happening inside you or around you, that occured in <1 second.
Being concrete, in ways that help you resolve confusion and gain momentum on solving problems.
Each stage of OODA Looping is quite deep
(i.e. "Observe", "Orient", "Decide", and "Act" each have a lot of deep subskills. The depth of "Noticing" is a subset of the overall set of "Observation" skills")
Feedback loops I think are the principle bottleneck in my skill development, aside from the fact that if you're a novice you don't even know what you should be noticing (even if you have enough awareness to be cognizant of all signs and outputs of an act).
To give an example, I'm currently trying to learn how to generate client leads through video content for Instagram. Unless someone actually tells me about a video they liked and what they liked about it, figuring out how to please the algorithm to generate more engagement is hard. The only thing that "wor... (read more)
For people asking about ‘noticing 5 things happening within a second or so’, you can see at least one (fictional but representative) example in Scaffolding for "Noticing Metacognition"
4Raemon
The "you need to hit a particular activation level" seems right to me. Generally when I'm trying to teach people skills, I try to get them to fluency-escape-velocity, where it is net-positive to apply the skill to their day-job.
There's additional important bits about hitting particular thresholds allow you to build engines out of multiple skills (I'll probably reply more to t14n's comment about that)
This is an experiment in short-form content on LW2.0. I'll be using the comment section of this post as a repository of short, sometimes-half-baked posts that either:
I ask people not to create top-level comments here, but feel free to reply to comments like you would a FB post.