• Author: [[George Polya]]
• I just bought the book. It’s $10. Not expensive. But the value it brings is huge. Worth it.

• Key notes

  • Chap 1

    • Problem solving is a muscle. The more we practice solving problems, the better we are.
    • Problem solving is like swimming. We learn by imitating and practicing.
    • The teacher who wishes to develop his students’ ability to do problems must instill some interest into their mind and give them plenty of opportunity for imitation and practice.
    • 4 steps of problem solving:
      • Understand the problem logseq.order-list-type:: number
        • What is the unknown? logseq.order-list-type:: number
      • Devise a plan - connect the data, the condition, the unknown logseq.order-list-type:: number
        • Have you solve a similar problem before? logseq.order-list-type:: number
      • Carry out the plan logseq.order-list-type:: number
        • Can you prove it’s correct? logseq.order-list-type:: number
      • Look back logseq.order-list-type:: number
        • What have you done good and bad? logseq.order-list-type:: number
        • Can you derive the result differently and extend this problem? logseq.order-list-type:: number
    • The teacher should be in his student’s shoe, to help him understand and devise the plan better.
    • Do by example.
    • Could you restate the problem?

• Quotes

  • “If you cannot solve a problem, there is an easier problem that you cannot solve.”
  • “The main danger is that the student forgets his plan. This may easily happen if the student received this plan from outside, and accepted it on the authority of the teacher, but if he worked for it himself, even with some help, and conceived the final idea with satisfaction, he will not lose this idea easily.”
  • “The teacher may ask: Can you see clearly that the triangle with sides x, y, c is a right triangle? To this question, the student may answer honestly “yes”, but he could be much embarrassed if the teacher be not satisfied with the intuitive conviction, then go on asking: But can you prove that this triangle is a right triangle? Thus, the teacher should suppress this question for now.”
    • Reflect on myself, sometimes I ask questions that dive very deep into one side of the problem, and it goes beyond my initial intention - just want to provide more knowledge to the student. Most cases it’s not good.
    • Because it kills the interest.
    • Don’t dive deep too much, just enough to get the student’s interest. This is more important.
  • “It is better to solve one problem in five ways, rather than solve five problems in one way.”

• https://www.1keydata.com/datawarehousing/datawarehouse.html
• https://www.kimballgroup.com/data-warehouse-business-intelligence-resources/kimball-techniques/kimball-data-warehouse-bus-architecture/

• j

Job To Be Done & Job Map

• [[[dblineage] Gathering User Data]]

• JTBD: Bridge the knowledge gap between business users and team data

  • When I’m a data engineer work with business users to build a ETL pipeline
  • I want to close the gap for business users who need to understand the fine-grained logic within those transformations.
  • They’re left wondering, “Okay, I see this column came from that column or that table, but how was it calculated? If so, can I trust?”
  • So that I and data team can brainstorm, design, discuss, and align on the same business logic

• Job Map

• https://media.secondbrain.lelouvincx.com/2026/02/7ba1920a32ca2377371db8243f9adbdc.png
• A mental model from Data - Information - Knowledge - Wisdom. By always being curious (asking why) and actively seeking for answers, connecting the dots and understanding the core / foundation / concept of things.
• Inspired by this article: https://campedersen.com/ownership-mindset

Keynotes

• Dimensional modeling structures data in the way business people think about it, rather than how softwares store it

Resources

• Figma: https://www.figma.com/design/1mU3qmVzCvjm2CXve978I0/Docs-Graphics

• Gemini: https://gemini.google.com/app/786f401ad9ba4ae8

• I realize when doing a task, I often become too over-engineer, lag, time-consuming and not focusing into the main task.

• This happens very often.

• Symtomps

  • Over-engineering: Spending hours writing perfect things that could have been a simpler one.

  • Yak shaving: When I want to fix a dashboard, but first I decide to update my dotfiles configuration, which leads to debugging neovim issue, and suddenly 3 hours have passed without touching the dashboard.

• https://media.secondbrain.lelouvincx.com/2026/03/4c39491a1814c0e767c359321242ad2d.png
• Lý thuyết bàn tay vô hình
  • Giá của một mặt hàng đúng với giá hợp lý của xã hội đặt cho nó
• Mình nhận ra lịch sử ảnh hưởng rất nhiều vào kinh tế của một nước
  • Trong chương đầu, học về cách mạng Mỹ, cách mạng Pháp, Napoleon
• Mối quan hệ giữa lợi nhuận và tiền lương là một trò chơi có tổng bằng không
  • Nếu tỉ lệ lợi nhuận của chủ doanh nghiệp tăng lên thì phần dành cho tiền lương của người lao động tất yếu phải giảm xuống và ngược lại
• Thị trường tự do là một assumption các nhà kinh tế học đặt ra để tính toán trên đó dễ dàng hơn
  • Ngoài đời thì khác hơn nhiều, một thị trường khó có thể tự do vì tồn tại rất nhiều kinh doanh độc quyền