• Being an expert requires experience.
• Approach to learning: Establish a workflow (Git, VScode, Vim, …) -> Build small projects -> contributing to OSS.
• Stay updated with what you are working on RN. Don’t try to stay up to date with everything that’s hapenning.
• Contribute to things you do use (it give you Motivation/empathy).
• Fundamentals don’t change as fast as we think.
• Don’t seperate soft and hard skills. They are just skills and they all matter.
• How to estimate time, Good questions:
  • Who’s waiting for this? where is the real world time pressure coming? (external deadline, customer, …)
  • There is no way you can do the entire feature by the deadline. What parts are critical, and what’s are nice to haves. (Prioritize)
  • Articulate the risks. State the worst case scenario (for example, something can happen to you, how much time will it take for someoe else to do the work)
• Write an email as if everyone in the work will be reading it. (don’t put something you don’t want people to see you say in RL)
• The most meaningful questions come after meaningful work (Spending a whole day trying things, googling, getting experience…). Here is what I did and here is my question.
• How much money is in the meeting (in term of how many people are attending the meeting) => Are all these people required to be present.
• Inspire instead of boss.