Vlad's Roam Garden
Powered by
🌱Roam Garden
reference
This is an "Orphan" page. Its core content has not been shared: what you see below is a loose collection of pages and page snippets that mention this page, as well as snippets of this page that were quoted elsewhere.
Referenced in
all code in the function should be at the same level of abstraction
reference
What does it mean to be a rationalist?
reference
[[§]] Programming your environment
reference
apply Spaced Repetition to evergreen notes that you want to remember or periodically rise to attention
reference
Deliberate Practice in West Coast Swing
reference
evergreen notes should be concept oriented
reference
when you develop software you invent a language
reference
the meaning of the code abstraction should be obvious from the call site
reference
evergreen notes should be written as if you were explaining the idea to a friend
reference
deep thinking requires external scaffolding
reference
Write shy code
reference
not stating your preferences clearly - imposes high computational costs on people you're communicating with
reference
functions should be small
reference
evergreen notes are the ideas or a thoughts elaborated in their full form
reference
asynchronous individual ideation is more effective than the group one
reference
Keep knowledge local
reference
context-switching is expensive
reference
intentional friend making
reference
Use explanatory variables
reference
readability can be understood in computational terms
reference
abstraction allows you to ignore irrelevant details
reference
use general-purpose language to augment your command line experience
reference
batch tasks to avoid unnecessary context switching
reference
Surround yourself with people you’d like to become more like
reference
externalize your thinking to free up your temporary memory
reference
worth of the decision is determined by expected value and not the outcome
reference
Vlad-interact hours
reference
transaction costs for delegation is high
reference
Spaced Repetition can be used for inbox maintenance
reference
To be able to speak eloquently on the topic - write about it first
reference
Expanding the Pie
reference
Marginal attention
isa::
attention
CFAR technique
make-public
reference
design defines cognitive problems users need to solve
reference
function size isn't important
reference
Streamlining my voice note process
reference
bad code kindles the urge to write comments
reference
prefer structure over convention
reference
Your friendly neighborhood botnet
reference
reduce the number of things you need to be aware of to understand any given code block
reference
Respecting level of abstraction
reference
To properly grok new information you need to actively engage with it
reference
translate novel ideas into the context of your thinking
reference
It's inefficient for people with high hourly income to do menial work
reference
people have a very limited short-term memory
reference
you should consider reading more in audio form
reference
macOS window switching
reference
when a group of values is passed around together it can indicate a missing concept
reference
Change your environment to encourage behaviors you want
reference
evergreen notes should surprise you
reference
treat challenges with writing unit tests as a feedback about your design
reference
employ the power of natural language to improve readability
reference
composite object interface should be simpler then sum of it's parts
reference
Close open loops
reference
consider constraining your system to give it desired properties
reference
Why I don't like "West Coast Swing"
reference
Even the best strategy sometimes yields bad results
reference
Spaced Repetition can be used to program attention
reference
spontaneous thinking vs deliberate thinking
reference
messaging layer as a service
reference
computation is bad
reference
good interfaces have small surface area
reference
Use Long Names for Long Scopes
reference
diffuse thinking mode
reference
reference