Chinh (lelouvincx) lelouvincx

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

Note

• Làm cái nào thì xong cái đó, done is better than perfect.

  • Không để task bị dồn ứ quá nhiều task, trừ khi bị pending/blocking bởi người khác.

• Done

  • DONE Nộp lại yêu cầu trích lục khai sinh

• DONE Raise issue with a Dat to fix the tenant’s version displays AI Enabled

• DONE Review & pause failure emails for a Khai

• DONE Answer chi Vy

• DONE Log debugging and tag anh Nui to slack

Note

• Holistics có 1 kho sách online do các anh chị push lên, đặc biệt là anh Thành.

• Giờ mới hiểu tại sao họ giỏi như vậy.

• Anh Thành là 1 người đáng ngưỡng mộ.

• Book reviews

  • The Design of Everyday Things
    • A seminal work in design theory that argues poor usability isn’t due to user incompetence, but rather design that ignores human psychology and cognitive principles. Norman uses everyday objects—doors, faucets, stoves—to illustrate fundamental design concepts.
  • The Mom Test - Rob Fitzpatrick
    • People lie in customer interviews - not maliciously, but because they want to be helpful and supportive.
    • The “mom test” asks: would your mom give you honest feedback, or just be supportive?
    • Who should read: product managers validating new ideas, early-stage entrepreneurs.
  • Designing Data-Intensive Applications - Martin Kleppmann
    • Comprehensive deep-dive into modern distributed systems architecture.
    • Focus on deep technical problems like distributed data challenges (replication, partitioning, transactions), batch/stream processing, data models, storage engines, encoding.
    • Who should read: senior software engineers, system architects, platform engineers, data engineers.
  • Grokking Simplicity - Eric Normand
    • Functional programming concepts through practical examples, focusing on separating actions, calculations, and data.
    • Who should read: Developers new to functional programming, javascript/typescript.
  • Don’t Think of an Elephant! - George Lakoff
    • Explores how political language shapes thought through cognitive frames and metaphors.
    • Who should read: Anyone interested in political psychology, marketing professionals, educators.
  • Bulletproof Problem Solving - Charles Conn & Robert McLean
    • Presents a structured 7-step approach to tackling complex problems, drawing from McKinsey consulting methods: (1) define the problem (2) disaggregate issues (3) prioritize issues (4) build workplan (5) conduct analysis (6) synthesize findings (7) communicate results.
    • Emphasis on hypothesis-driven thinking.
    • Who should read: analysts, anyone facing complex problems.
    • Helpful for senior data analysts.
  • Getting Things Done - David Allen
    • Presents a productivity system for managing tasks and reducing mental stress through systematic organization.
    • Who should read: Anyone feeling overwhelmed by tasks and commitments.
    • Claude said: this book is less useful for those preferring simple to-do lists over systematic approaches, someone find it too rigid.
      • My thought: is it true? worth reading.
  • A Philosophy of Software Design - John Ousterhout
    • Argues that software complexity is the root of most development problems and presents principles for managing it.
    • Teach principles like Clean Code.
    • Who should read: software engineers/architects.
  • Fundamentals of Data Engineering - Joe Reis & Matt Housley
    • Provides a comprehensive overview of modern data engineering practices and architecture patterns.
    • Need to be familiar with basic software engineering concepts.
    • Who should read: post junior-mid data engineers, software engineers transitioning to data.
    • Now I know it’s time to read this book, at my current level.
  • Storytelling with data - Cole Nussbaumer Knaflic
    • Teaches effective data visualization and communication principles.
    • Actionable design principles, Clear guidelines for chart selection, Practical before/after visualization examples.
    • Who should read: anyone presenting data.
  • The Speed Reading Book - Tony Buzan
    • Teaches techniques to read faster while maintaining comprehension.
    • Who should read: Anyone wanting to read more efficiently.

• Done

  • DONE Answer duty part 2

• DONE Check data import jobs

Note

• Happy new month!

• Done

  • DONE Document fixing for dim_tenants

• DONE Answer Vincent

• DONE Answer duty

• DONE Answer c Vy

• DONE Review Yen

Done

• DONE Gọi bố nhờ lên xã xử lý

• DONE Nộp lại giấy tờ cải chính

• DONE Correct inconsistent schema

• DONE Support Ryan Packer

• DONE Review tracking request

Done

• DONE Write 1on1

• DONE Merge and update dataset tagging_system with popover