Skip to main content

The most important thing in life

In life, you need to have a goal. How to achieve your goal?

You have to take action with a deep understanding of how reality works.

Your brain needs to have a map of reality. To create this mental map, you need to do the damn thing. This will create neural links. Then, you have to calibrate your mental map with reality. How? By constantly reflecting on what is true, what went wrong , what went right, then figure out the root cause and design a plan on how to do it differently in the future.

If you mental map is different from reality, your action will not be optimal. ie. You have the wrong belief.

You need to have a deep understanding of how reality works. To get there,

  1. You can learn from others (including books and in-person)
  2. You can learn by yourself (through your own experience or reasoning)
Learning by yourself can be slow. However, it will be a source of tremendous value because you reason from first principles. First principles are the basic truth, then you figure out from there. Learning from others can be a fast way, but leads to risk of getting the wrong truth (half truth). 

Certain things can make u deviate from your goal. Your craving and aversion. Your most usual craving includes:
  1. companionship and love
  2. respect, pride and ego
  3. physical comfort and gratification 
  4. habits / old ways of doing things that isn't always the right thing to do
Aversion includes:
  1. physical discomfort and pain
  2. fear (expectation of pain in the future)
  3. regret (reminiscent of pain in the past)
  4. unknown (risk)
What I think of life work is that it is like a game of dota. You have various factors to take into account. You have to take care and adhere to the max the most important factors. A few important factors:
  1. You have to work on a single thing for a long time in order for your neuron pathway to be strong. Also you have to generate learning point to learn. 
  2. Teams are one of the most important work structure, work well with a team and you could be unstoppable.
  3. Your self-interest should be lower than the ultimate interest.













Comments

Post a Comment

Popular posts from this blog

Problem Solving - Refactored

I am going to outline how I approach problem solving. The relative importance and the amount of effort/time required for each is stated as a percentage beside each topic. I borrowed some idea from George Polya's How to Solve It Thoroughly Understand the Problem (30%) When encountering hard problem , you need to deeply understand the problem at hand. Take a paper and list down all known facts and data and what the question is trying to find. Sketch out the problem if applicable. Visualize the problem in your head. A lot of times, we only have to understand the problem well, then the solution will obvious. Have a Plan (20%) You need to have an outline of how you are going to tackle the problem. You need to have a logical pathway that will ultimate produce outcome (nothing to do with coding syntax yet). Without a plan, you are just randomly poking around and got lucky. No hard problem ever gets solved without a plan. Plan using pseudo-code, pen & paper or flowchart. Use wh...
5 comments
Read more

Sharing my Weakness

It makes sense to know about your weakness and do something about it. Here are my known weaknesses uncovered during my time in Launch School. 1. I don't like to refactor my code   - Your first draft will not be perfect. It works but it may not be efficient/readable/best practices. You final code will almost always be better than your first draft. - It is easier to separate the task between writing code that works and refactor later to make it efficient/readable/best practices. - If you refactor your code often, over time you will discover your bad habits and change it. 2. I don't like to read other people's code - There are more good programming practices in other people than in you (especially for beginners like me). - To be good , you need to know more than one pathways to solve a programming problem (and there are always more than one way). Then you can judge their merit. - Reason for dislikes    1. It is considerably harder to read code than to write one (...
1 comment
Read more

My Burnout Experience

I want to share with you my experience of burning out. After registering with Launch School, I am extremely excited about my programming journey. I studied for 10 to 12 hours a day, memorizing fact, trying out practice problems, understanding programming concepts. It was fun and exciting and I love seeing myself growing from nothing in programming to something more. After about 3 months, thing starts to change. I started noticing myself paying less attention to details. I find myself skimming through the course material. I skip "Further Exploration" in the practice problem. I am more interested to study just to pass the assessment rather than truly mastering the concept. It was a gradual burning out process but I continue to study for 10 to 12 hours a day through sheer grit. It felt like doing house chore or working a day job that you don't like. One particular morning I woke up, and I remember this deep feeling of dread because I can anticipate that the next 10 to 1...
Post a Comment
Read more