3-1b1b Problems encountered during projects are valuable. The harder they are the better.
3-1b1a Often the real insight is in the question and not in answer
3-1d6d Consistency with specific problems in mind is the key to (detect) progress
3-1d6c Amara’s law modified - we underestimate the importance of consistency in the short-run, but overestimate in the long-run
5-1b4c Exponential growth feels flat in the beginning, precisely why it’s worth making an extraordinary effort to get it started. You can also follow the Fun Criterion (the latter likely exhausts the former). Consistency is the key.
7-1a2b For startups, growth is a constraint much like truth
5-2d2 You need somewhat grandiose goals to procrastinate structurally - テーマはひとつでは多すぎる
4-1a3 Each conversation has to end either a success or a failure, you have to zone-in when you are ‘friend-zoned’
5-1b1a4b The extreme version of the two-job route is dangerous, because you postpone the abductions
3-1c3d2a Chasing growth ≠ Listing off projects like todo
3-1c3d3 When problems are so well defined, your future self might be able to solve new problems by reusing and recombining them
RUL3 - Finish what you start, because the best work often happens in what was meant to be the final stage
RUL3 - Simplify the problem by deciding the “no-brainer” questions first
Learn AND Make ≠ Learn THEN Make
The point of packeting into mini projects is that it reminds you constantly of the problems you are working on, as well as the context (larger problem-situation) from which such problems (mini-projects) arise. It helps you solve the problem of what problems to solve at the same time.
3-1c1 Learning with intent to use them in the future (i.e., performance-output-oriented) filters down information, while constantly reminding you of the very problem-situation you are trying to solve and the very purpose that comes with it.
5-2b1a1 Your goals are gateway to your problem-situation, just like your concepts and categories are to your purpose and values