11–20 of 147 posts
Making an outline is also important for writing. However doing research also has its place. See this here https://cse.buffalo.edu/~rapaport/howtostudy.html#makeoutlin... (also previously discussed on HN)
This is a great article that summarizes a method I’ve already used for my work over the years. When writing a new project from scratch ill make a bunch of structure (defining modules, writing pseudo code) then start to fill things out piece by piece. Often times ill need to adjust the structure as I go but helps for building a mental model of a new project (at least for me)
This strategy can be applied to learning as well. The concepts are very similar to those presented in “How to Read a Book”[0]. The general gist is: create a mental outline of the book/material (via the table of contents), dive into interesting chapters, resurface to the outline, dive again, etc. This strategy is useful for quickly building a mental model and using your own interest as the guiding light. Similar to bu…
How to Read a Book, is ironically one of my favorite books. I attribute a lot of my ability to learn to this book and a teacher in high school that forced us to read and understand it.
This is a great article that summarizes a method I’ve already used for my work over the years. When writing a new project from scratch ill make a bunch of structure (defining modules, writing pseudo code) then start to fill things out piece by piece. Often times ill need to adjust the structure as I go but helps for building a mental model of a new project (at least for me)
Do you mind sharing a concrete example of one your project s?
By the way, for the programming case, this is a big part of the reason functional programming is so powerful. Avoiding shared state allows you to write your outline of smaller and smaller pieces, then write each piece as a stateless function, then pipe your data through a graph of these functions.
With other programming paradigms, you can't just knock out all the little pieces without thinking about the other pieces because the state is all tangled up. Which slows you down.
It's surprising how very simple the individual components can be, even for very complex systems, when following this approach.
The author provides an example of the bad "Loading bar writing" but unfortunately not a good example of what they call "Outline speedrunning writing" pg, who's good at writing essays, does provide a good example of the latter, with https://byronm.com/13sentences.html . This is the writing process that lead to https://paulgraham.com/13sentences.html . (the https://code.stypi.com/hacks/13sentences?doomed=true URL on pg…
Something similar to this is presented with much more details in Zerubavel's “The clockwork muse”, a highly recommended book.
This message is suspiciously like being told to draw the outline of an owl then draw the rest of the fucking owl. https://seths.blog/2014/01/how-to-draw-an-owl/ The word recursively does a lot of work in the post. Every project I go into thinking I can do it quick and it never works that way because the minimal viable or minimum lovable thing is a long way from the minimum actual concept of what I have in mind. I fee…
This strategy can be applied to learning as well. The concepts are very similar to those presented in “How to Read a Book”[0]. The general gist is: create a mental outline of the book/material (via the table of contents), dive into interesting chapters, resurface to the outline, dive again, etc. This strategy is useful for quickly building a mental model and using your own interest as the guiding light. Similar to bu…
- How to read a book by Adler
- How to read a paper[0]
- How to study[1]
Serves as an entrypoint and gatekeeper. Reminds me every time how to spend my time effectively there.