Live data from Hacker News

How to build quickly

learnhowtolearn.org

1–10 of 147 posts

Re: How to build quickly

#3
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 building quickly, the focus is on your attention/what’s most important, rather than traversing from the beginning to the end serially.

Great post!

[0] https://en.m.wikipedia.org/wiki/How_to_Read_a_Book

Re: How to build quickly

#4
I like this idea a lot! I’ll try it today. I think a version of this is how I, and most professionals(?) already work. But I do believe my process can be sharpened.

Re: How to build quickly

#5

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.

Re: How to build quickly

#6
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 feel that I need to build enough that the user is engaged with it.

I feel like those first explorers willing to try out a new thing are incredibly valuable and their attention should not be wasted on the outline, but they should be presented with the owl.

Re: How to build quickly

#7
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)

Re: How to build quickly

#8

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…

It feels like the article is describing how to draw an owl, but in reverse. You know what the owl should look like, and you simplify all the way down until each step is little more than a tiny pencil mark.

Re: How to build quickly

#9
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's blog is a now a dead link. Previous discussion: https://news.ycombinator.com/item?id=6993060).

Re: How to build quickly

#10

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…

The first explorers will to try a new thing, as you say, will also be quick to try the next new thing. So they’re probably less valuable than you’d expect.
Post reply on HN