Chinh (lelouvincx) lelouvincx

Note

• https://chatgpt.com/share/68c8c0e4-b398-800d-9c65-c7c9ed828d29

  • [[Metacognition]]: suy nghĩ về suy nghĩ.
    • Dừng lại để suy nghĩ về chính suy nghĩ và cách làm của mình.
  • Mình nhận ra bản thân [[Probability|xác suất]] cũng là 1 dạng metacognition.
    • Vì xác suất là dùng để đo lường mức độ không chắc chắn (uncertainty) != tỷ lệ.
    • Nhiều học sinh không hiểu bản chất này, vì bản thân sự không chắc chắn khó hình dung một cách hữu hình.
    • Vì vậy lúc lên cao hơn, làm việc với các đại lượng của xác suất và thống kê (kỳ vọng, độ lệch chuẩn), nó khó, giáo viên và học sinh thường tối giản nó bằng cách đưa về bài toán giải tích & đại số => mục đích để giảm cognitive load - aka một cái workaround.
    • Chính cái workaround này khiến sự việc tệ đi - không hiểu bản chất của xác suất từ đầu.

• 

• Note

  • [[Book - Getting Things Done]] key notes.
    • Commitment management (expectation management).
    • First of all, if it’s on your mind, your mind isn’t clear. Anything you consider unfinished in any way must be captured in a trusted system outside your mind => from that you can come back to regularly and sort through.

• Done

  • DONE Check for Simon https://holistics.slack.com/archives/C07JKMWBF7G/p1757675453842069?thread_ts=1757326032.949539&cid=C07JKMWBF7G

Note

• Today I ran across this article: https://addyosmani.com/blog/chrome-17th/

  • TL;DR: Documentation about the history of Chrome Browser.
  • I think it’s interesting, then ask claude to review, who should read and when to read.
  • Claude’s answer:
    • This is a comprehensive technical memoir by Addy Osmani, a Chrome team member at Google, chronicling Chrome’s 17-year evolution through its four core principles: speed, security, stability, and simplicity.
    • Primary Audience:
      • Web developers and engineers - Deep technical insights into browser architecture, web APIs, and platform evolution.
      • Product managers in tech - Strategic decisions behind Chrome’s feature development and market positioning.
      • Browser/web technology enthusiasts - Insider perspective on major innovations like multi-process architecture, V8 engine, Site Isolation.
    • Ideal Timing:
      • During technical research - When studying browser architecture, web security, or performance optimization.
      • Career preparation - Before interviews at browser companies or web platform roles.
      • Learning web standards - When diving into PWAs, Web APIs, or Project Fugu capabilities.
      • Understanding AI integration - Current insights into browser AI features and local ML models.
  • So I wonder, this may not the good time to read right now. How can I create a reminder to remind me when the better time comes?

• https://bevel.work/blog/just-enough-automation/

Note

• Think about run evaluate against a context-enriched dataset vs. a raw dataset.

• Nhà sách Cá Chép sắp dừng hoạt động. Tranh thủ có giảm giá 80%, mình ra mua vài cuốn, đồng thời ra nhìn nhà sách lần cuối trước khi đóng cửa.

• Done

  • DONE Lên trường hỏi nộp lệ phí tốt nghiệp

• DONE Double-check tests cases again

• DONE Answer Simon

Note

• Silence like water - the idea from [[Book - Getting Things Done]]

• https://chatgpt.com/c/68c2f1bd-db54-832a-9a37-6c2a11dd0501
• Building concentration is like building muscle - the more train, the stronger it gets.
• I’ll get started with going from bottom-up to get the basic mental model. When I get used to it I will learn the harder levels.
• Goals:
  • Train awareness, notice distracting factors, gently bring the mind back.
  • How good enough should I move on the next exercise?
• Very basic methods:
  • Build basic attention + awareness of distraction: [[Breath Counting]]
  • Build visual focus: [[Single Object Focus - Just Observe]]
  • Build auditory focus: [[Sound Anchoring]]

• Done

  • DONE Review & refine questions

Done

• DONE Review (questions + evidence) and inform anh Dat

• DONE Answer review PR DAT-449

• DONE Review dataset setup for Mawave

• Done

  • DONE Chụp ảnh thẻ: 2 ảnh 3x4

• DONE Photo + công chứng bằng cấp 3

• DONE Nộp hồ sơ xét tốt nghiệp

Note

• https://www.metabase.com/data-stack-report-2025

  • The interesting thing of this is that they include embedded visualization, implicitly promote their embedded analytics feature.
  • 🤔 Don’t know how high interaction and target readers of this kind of article.

• https://bbycroft.net/llm

  • Pretty cool LLM inference’s visualization.

• Education is not the learning of facts but the training of the mind to think. ~ Albert Einstein

• https://share.google/aimode/I5Nx95BpXewJrNQrv

  • Main thinking skills:
    • Critical thinking.
    • Problem solving.
    • Analytics thinking.

• Education is what remains after one has forgotten what one has learned in school.

• Note

  • https://minds.md/zakirullin/cognitive
    • But what’s worse? When you come back later you would have to recreate that thought process.
    • School courses are design going step by step is to reduce the burst of cognitive load from day one.
      • What I am teaching is letting them know all from the start. Is it good?
    • Another metric to measure productivity (beside priority): cognitive load?

Note

• https://www.seangoedecke.com/the-simplest-thing-that-could-possibly-work/
  • System design requires a lot of different tools: backend, frontend, database, cache, proxy, queue, etc. As they gain more familiarity with these tools, juniors naturally want to add them up. To them, it’s fun to construct systems out of many different components - feels satisfying to place lego blocks on a whiteboard - like they are doing real engineering.
  • Have you ever thought something like “oh, I didn’t realize the problem was that easy” or “oh nice, you don’t actually have to do anything difficult”.
  • The industry-standard Rails REST API is great software design, because it gives you exactly what you need for a CRUD app in the most boring way possible. I don’t think any of these are impressive software. But they’re impressive feats of design, because they do the simplest thing that could possibly work.
  • Start with the absolute simplest thing, and then only extend it when you have new requirements that force you to.
  • When you’re looking at a problem, the first few solutions that come to mind are unlikely the simplest one. Figuring out the simplest solution requires considering many different approaches.
    • In other words, it requires doing engineering.
    • What is “doing engineering” actually?
  • Kim chỉ nam: Simple systems are stable.
  • 2 ways to develop software:
    • The first is to predict what your requirements might look like six months or a year from now, and then design the best system for that purpose.
    • The second is to design the best system for current requirements.

• Everything should be made as simple as possible, but not simpler. ~ Einstein