Planning the right way is hard. The right way - to me - is to come out with a plan that * has a right balance between achievable and almost-achievable (stretch goal) * has data and reasoning for people to understand, buy-in and execute * has defined success metrics (if applicable) * has compelling

Điều thử thách (vietsub từ "the hard thing" trong tựa sách "The hard thing about hard thing" [https://www.amazon.com/Hard-Thing-About-Things-Building/dp/0062273205]) * Điều thử thách chưa hẳn là làm quen được với 1 ngôn ngữ mới, mà hiểu nó khác gì so với ngôn

Ever realize that you spend more time in updating the applications/tools or customizing/tweaking the tool than in actually using it ? Ever realize that you prefer to read a Facebook post than a long form article in the newspaper ? Ever think about why you like to buy stuffs -

1. Prioritize product roadmap * When a customer says something is critical, be able to verify how much critical it actually is based on your domain knowledge of that team’s function and the related team’s function * Be able to differentiate between “noises” and “valid request” (customers will always make