Site index
Sitemap
Every article and note on this site, grouped by topic. Browse the list, or jump straight to something you remember reading.
Main sections
Back to topBlog articles
205 articles in 5 categories.
Series
Source & Architecture42
- The First Five Minutes of a System Design Interview
- Designing Defaults That Fail Safely
- Keep Data Contracts Small Enough to Trust
- Choose Boring Boundaries, on Purpose
- Design the Escape Hatch Before Someone Builds a Back Door
- Let the Interface Tell the Truth When the System Is Struggling
- Designing for the Change You Can Actually See
- Name a Boundary, Then Give It Examples
- Keep Architecture Decisions Small Enough to Revisit
- Interfaces That Outlive the Code Behind Them
- Refactoring Toward a Clearer Core, One Small Step at a Time
- Architecture Decision Records for Your Future Teammates
- Choose the Boundary Before You Choose the Tool
- Observability Is a Design Decision
- The Outbox Pattern: Stop Losing Events Between Commit and Publish
- Do You Need a Service Mesh? Ask Your Incidents First
- Event Sourcing for Beginners: Keep the Whole Story
- CQRS: How Far Should You Split Reads From Writes?
- Serverless Trade-offs: What You Hand Over and What You Still Own
- Caching Strategies and the Pitfalls That Bite Later
- Database Sharding: When It's Worth It and What It Costs
- GraphQL or REST? Start With Who Shapes the Data
- Designing APIs That Survive the Second Click
- Rate Limiting and Throttling Without Punishing Real Users
- The Saga Pattern, or How to Undo Half a Checkout
- What Belongs in Your API Gateway (and What Doesn't)
- Hexagonal Architecture on One Real Feature, Start to Finish
- Eventual Consistency Is a Promise About Time
- Dependency Direction in Plain Language: Which Way Should Your Imports Point?
- Layered or Vertical Slices? Follow Where Your Changes Land
- The Real Bill for Microservices, Line by Line
- Scaling a Database: Climb the Ladder Before You Shard
- Observability at Scale, One Request at a Time
- Event-Driven Architecture, Explained Without the Hype
- Who Owns the Data Once Your Services Split Up?
- Timeouts, Retries and Circuit Breakers: Stop One Slow Service From Taking Down the Rest
- Ports and Adapters, Explained With One Checkout
- Clean, Onion and Hexagonal Architecture Are One Rule Drawn Three Ways
- Dependency Injection and Inversion of Control, Without the Magic
- Group Code by Feature or by Layer? Let the Next Change Decide
- When to Split a Monolith Into Microservices (and When to Wait)
- When Micro-Frontends Are Worth It (and What You Pay)
Engineering Culture41
- Protecting Focus in a Busy Team
- Notice Friction Before It Turns Into Blame
- Making Room for the Reviewer Who Doesn't Speak First
- What Good Ownership Looks Like Day to Day
- Ask for Help While the Problem Is Still Small
- Why Good Teams Surface Risk Early (Without the Panic)
- What Small Code Reviews Teach Your Team
- How Trust Grows in Ordinary Follow-Through
- How to Say "Not Yet" to a Release Without Becoming the Blocker
- Your Reviewer Is the Code's First Future Reader
- When Silence in a Team Becomes a Signal
- How to Ask for Help So It's Easy to Say Yes
- A Simple Script for Hard Feedback Conversations
- Innovation in Teams Starts With Noticing Friction
- Office Politics, Played in Daylight
- Mentorship vs Sponsorship: Who Talks With You, Who Speaks Up for You
- What to Celebrate When Something Breaks
- Diverse Engineering Teams Start After the Offer Letter
- Managing Up: Talking to Non-Technical Leaders
- Performance Reviews People Can Actually Use
- How to Catch Burnout Before It Catches Your Team
- A Blameless Culture Starts in the First Minute of the Postmortem
- Giving Constructive Feedback People Can Use
- Onboarding That Actually Helps New Teammates
- Async Communication for Remote Teams
- When Your Best Engineer Is Hard to Work With
- Hiring for Potential or Experience? Look at the Evidence First
- Pull Requests Reviewers Can Approve Without Guessing
- How to Run a 1:1 Worth Showing Up For
- When "Not a Culture Fit" Really Means "Not Like Us"
- Sitting With a Problem You Can't Solve Yet
- Pull, Don't Push: Hand Over the Why With the Work
- Signals or Messages: Why "Can We Talk?" Ruins a Weekend
- Why a Vision Needs a Feel for the Work
- When a Busy Team Is Over-Managed and Under-Led
- From Software Engineer to Technical Manager: Three Habits to Rewrite
- How to Review Code Kindly (and Still Catch the Bugs)
- Kind Engineers Still Say the Hard Thing
- How to Write a Pull Request That’s Easy to Say Yes To
- How to Give Feedback, and How to Take It
- How to Mentor Engineers Without Doing Their Work for Them
AI & The Future40
- Let AI Widen the Search. Keep the Judgment.
- Ask the AI to Name Its Assumptions First
- Treat AI Suggestions as Draft Evidence
- Keep AI Changes Small Enough to Actually Review
- Let AI Write the Boring First Draft
- Ask Your AI Assistant What Its Answer Stands On
- Letting AI Draft While Humans Keep the Map
- What AI Can't Know From the Prompt Alone
- Using AI Without Handing Over Your Judgment
- Using AI to Read a Codebase You Didn't Write
- From a Great AI Demo to Behavior Users Can Depend On
- The Feedback Loop That Makes AI Work Better Every Week
- The Cost of Trusting a Fluent AI Answer
- What a Vector Database Actually Does, and Where It Trips Up
- AI in Cybersecurity, on Both Sides of the Alert
- Reducing Hallucinations in LLMs, One Layer at a Time
- AI in QA: Generating Tests That Actually Catch Bugs
- What a Local LLM Keeps Private, and What It Doesn't
- AI Agents Should Earn Their Autonomy
- Before You Paste That Ticket Into an AI Tool
- Multimodal AI: What Changes When the Model Can See and Hear
- Using AI to Refactor Without Changing What the Code Does
- How to Evaluate an LLM Feature Before Your Users Do It for You
- Prompting, RAG or Fine-Tuning? Name the Failure First
- Ethics in AI Products Starts in the Feature Brief
- RAG Basics: Search First, Answer Second
- Why Long AI Chats Lose the Thread
- How Much Testing Does an AI Answer Need?
- Prompt Engineering Is Mostly Clear Communication
- What LLMs Actually Understand (and What They Don't)
- Three Levels of AI Literacy, From Prompts to Agents
- Cognitive Debt: When AI Writes Code Faster Than Your Team Can Understand It
- Your Fear of AI Is About the Size of Your Plans
- From SDLC to ADLC: What Changes When Agents Write the Code
- Small AI Workflows That Actually Save You Hours
- Five AI Shifts Worth Your Time in 2026 (and What to Do With Them)
- What an AI Agent Actually Is, and How Much Rope to Give One
- How AI Is Changing Every Role on a Software Team
- Everyday Generative AI, From Awkward Emails to Dinner Plans
- Context Engineering Is Briefing a Smart New Hire
Perspectives & Field Notes32
- Where to Eat in Vietnam: I Built an App That Picks One Place
- What Thirty Days of Small Notes Can Teach You
- Done Means Someone Else Can Pick It Up
- Find the Way Back Before You Decide
- Wait for the Whole Story Before You Call It
- Sometimes Progress Means Taking Things Away
- The Relief of Finally Naming the Problem
- Carrying Uncertainty Without Stalling the Work
- What Vague Words Cost Your Team
- The Case for a Slightly Slower First Answer
- Why Consistency Compounds
- The Difference Between Confidence and Evidence
- The Note You Come Back To
- It Takes a Little Nerve to Write the First Rough Note
- When You're the Only Developer on the Project
- One New Language a Year, No Fluency Required
- How to Get Unstuck From Analysis Paralysis
- When to Walk Away from a Project
- What Actually Multiplies When We Call Someone 10x
- What a Small Side Project Teaches You
- Switching Into Tech Without Starting From Zero
- Working With Legacy Code Without Starting Over
- Commit Messages That Explain the Why
- Why I Love Writing Documentation
- Reading Code Is Harder Than Writing It
- What Junior Developers Actually Need From a Mentor
- The Case for a Boring Tech Stack
- Perfect Code Is the Wrong Target
- Why Good Preparation Looks Like Nothing Happened
- Saying No as a Developer Without Becoming the Difficult One
- Breaking Production for the First Time
- Hoang Nguu Son: Reach the Summit, Come Down, Keep Going
Ways of Working50
- Keep what your code reviews learn
- Making Handoffs Honest About What Is Unknown
- Keep Checklists Close to the Work
- Status Updates People Can Actually Act On
- Close the Loop Before You Start the Next One
- Keep Meeting Notes Close to the Decisions They Made
- Writing Next Steps That Actually Help
- Making Handoffs Easier to Receive
- A Fuzzy Request Deserves One Shared Page
- When Scope Changes, Ask What Moves Out
- Managing Dependencies Without Finding Someone to Blame
- A Decision Log Busy Teams Will Actually Keep
- When the Roadmap Meets Real Capacity
- Cross-Functional Teams Work When They Share One Outcome
- Engineering OKRs That Measure Real Change
- Trunk-Based Development: Merge Small, Merge Daily
- Definition of Ready vs. Done: Safe to Start, Honest to Finish
- Pair Programming: Love It or Hate It?
- Feature Flags: Deploy Today, Release When You're Ready
- Continuous Integration vs. Continuous Delivery
- Shift-Left Security Starts With Better Questions
- Behavior-Driven Development: Agree on Examples First, Automate Second
- Seven MVP traps, and the question that gets you out of them
- Is TDD Worth the Time? What the Evidence Says
- Retros That Actually Change How the Team Works
- Writing Acceptance Criteria People Can Actually Test
- Kanban or Scrum? Start With How Work Reaches Your Team
- The Daily Standup That Changes Decisions
- Agile Is Dead, Long Live Agile
- Daily Standup: Stop Reporting, Start Walking the Board
- Requirements after sign-off: quality, traceability and checking that it worked
- Lean BA Planning: Who to Learn From, and How
- Requirements Modeling: Five Kinds of Pictures That Catch Gaps Early
- Lean Business Analysis: Start with the Need Behind the Request
- Software Measurement and Estimation: Numbers That Help You Decide
- Agile Estimating and Planning: Treat Every Estimate as a Conversation
- Agile Release Planning That Bends Without Breaking
- Design of Everyday Things: Screens That Explain Themselves
- Data: Revenue Isn't Cash, and Neither Is Paper Profit
- When “Human Error” Is Really a Design Problem
- Data: Everyone Has a Number, So Nobody Has to Guess
- Data: Your Numbers Should Work Like a Clean Windshield
- Data: A One-Page Scorecard That Spots Trouble Early
- Pre-Mortems: Ask Why the Plan Failed Before You Start
- Working in a Startup, Where Ambiguity Is the Job
- Working in software outsourcing: scope, clients and shipping on contract
- Big Corp, Startup or Outsourcing: Same Title, Different Job
- Working in a Big Corp Without Feeling Like a Cog
- TDD, BDD, DDD and the Rest: What Each "-Driven" Actually Drives
- How Scrum Really Runs, from Story Points to Retros
Notes
135 notes, grouped by topic.
Career & Growth19
- Trust Is Earned, Not Staged
- Before Working Harder, Check Whether the Direction Can Grow
- When Someone Else Succeeds, Do Not Let Your Own World Become Smaller
- Tang Sanzang Holds the Vision: A Leader Does Not Need to Do Everything, but Must Keep the Direction
- Sun Wukong at Work: 10x Talent Needs Room to Move and Clear Boundaries
- Zhu Bajie, Sha Wujing, and the White Dragon Horse: Quiet Roles That Keep a Team Moving
- Journey to the West as a Project Team: Every Hard Stretch Teaches Coordination
- Liu Bei and People-Centered Leadership at Work: Trust Must Become Behavior, Not Just Warm Words
- Cao Cao and Rule-Based Management at Work: Good Systems Help Teams Stop Managing by Emotion
- Between Liu Bei and Cao Cao: Work Needs Humanity, but It Also Needs Clear Rules
- In Front of People Who Can Lift You, Be Honest
- Echology Check: Testing an Idea Before It Distorts the Ecosystem
- Employee Happiness Often Starts with Meaningful Results
- Respecting Others: Looking Back at Myself Before Judging
- Receive, Hold, Break: Learning Without Getting Trapped by What I Know
- Living Many Roles and the Cost of Whole-Life Change
- Work With Care: Becoming Worth Trust Before Asking for Bigger Roles
- Beneath a Photo Caption: BonBon, a $500K Round, and What a Co-founder Learns
- Owning Your Career: Turning Work into a Long-Term Platform
Book Notes19
- The Art of Thinking in Systems: Do Not Fix the Symptom and Call It a Solution
- The 7 Habits: Personal Effectiveness Begins With Keeping Promises to Yourself
- Atomic Habits: Big Change Often Begins With a Very Small System
- How to Win Friends and Influence People: Good Communication Begins When We Stop Making Ourselves the Center
- The World Is Flat: A Flatter World Is Not Automatically an Easier One
- The 360° Leader: Leadership Starts With Influence, Not a Title
- The 360° Leader: Leading Up Is Not Managing Your Boss
- The 360° Leader: Leading Across Means Helping Peers Win
- The 360° Leader: Leading Down Means Growing People
- The Visual MBA: Reading Business as a System That Has to Run
- Thinking, Fast and Slow: Catching My Mind Moving Too Quickly
- Game Theory: Wise Cooperation Is Not Giving Away the Win
- The Alchemist: The Long Road Back to What Was Already Yours
- Criminal Psychology: Learning to Read the Smallest Clues Carefully
- Think and Grow Rich: Desire Is Only Useful When It Becomes a Written Plan
- The 48 Laws of Power: Reading Power Without Becoming Cold
- David Eagleman on the Adaptive Brain: The Mind Learns Through Signals
- How to Change by Katy Milkman: Durable Change Starts in Small Places
- Never Eat Alone by Keith Ferrazzi and Tahl Raz: Relationships Are Built Before You Need Them
Perspectives & Reflections33
- Wisdom Needs Character So It Does Not Become a Sharp Knife
- Clarity Is a Form of Strength
- The Highest Strategy Is Not Winning the Battle, but Understanding People
- Lines Collected Along the Way: A Second Brain for Reminding Myself
- Seeing Human Nature More Clearly in Friendships
- The Pause Between Feeling and Response: Where Better Choices Begin
- The Foundation Comes First: Visible Progress Is Built Before Anyone Notices
- Two Ways of Thinking: How Induction and Deduction Shape Work and Relationships
- Fifteen Quiet Rules for Moving Through Work and Life
- Seven Quiet Principles for Doing Meaningful Work
- Working Calmly With People You Find Difficult
- Forgiveness Is for You: Setting Down a Weight You No Longer Need to Carry
- Your Salary Is Seed Capital, Not the Finish Line
- You Are Not a Machine: Why Rest Is Part of Doing Good Work
- Things Experience Slowly Teaches You
- The Approval Loop Has No Finish Line: Five Quiet Ways to Come Back to Yourself
- The Person Who Does Not Need to Prove It: Quiet Strength Without Performance
- Steady Presence: The Quiet Authority of People Who Hold Balance
- How People Actually Work: Fifteen Quiet Notes About the Human Mind
- Choice and Circumstance: Living Well Inside What You Cannot Fully Control
- The Old Man Who Lost His Horse: Hold the Verdict, Keep the Present
- Complexity Is Inevitable, Simplicity Is Sustainable: Lessons from Systems and Life
- Same Facts, Different Story: Position and Language Change the Experience
- From Idea to Follow-Through: The Quiet Practice of Not Stopping
- The Quiet Art of Letting Go: Seven Shifts of a Maturing Mind
- What C-Level Leaders Learn Before the Chair: Five Practical Roads in Big Corp
- The Quiet Strength of People Who Walk Alone
- The Meaning of a Life Is in the Living: A Gentle Case Against Waiting for Later
- Know the Map: Why Understanding Your Career Path Is an Engineer’s Quiet Advantage
- Deciding to Marry: 24 Conversations Before You Share a Home
- A Groom’s Practical Guide to Wedding Preparation: Stages and Budget in Vietnam
- Know Your Rights at Work: Quitting, Switching Jobs, Insurance and Tax in Vietnam
- The Monkey, the Bananas, and the Eight-Hour Question
Thought Garden40
- Why Work Messages Can Feel Sharper Than Intended
- When Information Consumption Replaces Action
- A Reading System
- Anchoring on Tool Capability Limits the Mind
- Be Mindful of What You Put Into Your Bucket
- Does Code Still Run on People?
- The Completeness Learning Bias
- The Different Purposes of Writing
- Feel the Sensation
- Healthy Disagreement
- How I Write Notes
- The Human Advantage: Brain Elasticity vs. Frozen Weights
- Indecisiveness
- What I Would Tell My 20-Year-Old Self
- Life Running on a Digital Engine
- Modal Thinking: Separate Deciding From Doing
- Play the Game
- The Programmable Self
- Programming Abstractions Are Bets
- Programming Beacons
- The Purpose of Highlights
- Reading Is Catching Balls
- Are There Recognizable Patterns of Valuable Thoughts?
- Sense
- Software Engineering Fatigue
- Start New Behaviors in Boring, Easy Mode
- The Cost of Delayed Action
- The Heuristics for 'What To Do Now'
- The Thinking and Doing Rhythm
- When Thinking Becomes the Excuse
- Trust
- A Rich, Consistent Vocabulary Is the Best API for Your Second Brain
- What If I Founded a Startup
- Write to Attend
- Write to Understand and to Transfer
- AI Reduces the Information Advantage
- Why Taking Notes?
- Perfect-Tools Syndrome
- Articulation Skill
- The Physics Laws of Life
Personal Finance & Saving11
- Budgeting and Cash Flow: A Gentle Map for Every Dollar You Earn
- Emergency Funds from A to Z: A Buffer for Unplanned Shocks
- Getting Out of Debt Wisely: Step by Step Through High-Interest Debt
- Investing for Beginners: Starting from a Stable Foundation
- Inflation and Purchasing Power: Why Money Needs Protection Over Time
- The Right Insurance: Buying Protection, Not Anxiety
- Avoiding Investment Scams: Recognizing Risk Before Sending Money
- Personal Finance by Age: What to Prioritize in Your 20s, 30s, and 40s
- Money in the Family: Talking About Finance Calmly
- Financial Prosperity: A Path for Money to Slowly Work for You
- Keeping Money in Your Pocket: Protecting the Value You Create
Home Buying12
- Borrowing for a Home: Using Leverage with Clear Eyes
- Valuation and Negotiation When Buying a Home: Pay with Evidence, Not Emotion
- Location and Planning When Buying a Home: The Hardest Thing to Fix Later
- The Home Buying Process from A to Z: A Slow Map for First-Time Buyers
- Apartment, Landed House, or Project Home: Choose by the Way You Live
- Reading House Plans and Evaluating Build Quality: Seeing What Photos Do Not Show
- The Psychology of Buying a Home: Keeping Distance from Fast-Closing Pressure
- The Full Cost of Buying a Home: Seeing the Whole Picture Before Paying
- Risk Scenarios When Buying a Home: Loans, Deposits, and Disputes
- Real Estate Legal Checks: What to Review Before Paying
- Feng Shui When Buying a Home: Reading Light, Air, and Daily Habits
- What to Think About When You First Consider Buying a Home
Cars & Major Purchases1
Archive pages
- Blog, Page 2
- Blog, Page 3
- Blog, Page 4
- Blog, Page 5
- Blog, Page 6
- Blog, Page 7
- Blog, Page 8
- Blog, Page 9
- Blog, Page 10
- Blog, Page 11
- Blog, Page 12
- Blog, Page 13
- Blog, Page 14
- Blog, Page 15
- Blog, Page 16
- Blog, Page 17
- Blog, Page 18
- Blog, Page 19
- Blog, Page 20
- Blog, Page 21
- Blog, Page 22
- Blog, Page 23
- Notes, Page 2
- Notes, Page 3
- Notes, Page 4
- Notes, Page 5
- Notes, Page 6
- Notes, Page 7
- Notes, Page 8
- Notes, Page 9
- Notes, Page 10
- Notes, Page 11
- Notes, Page 12
- Notes, Page 13
- Notes, Page 14
- Notes, Page 15
- Foundations of Software Architecture, Page 2
- Career & Growth, Page 2
- Career & Growth, Page 3
- Book Notes, Page 2
- Book Notes, Page 3
- Perspectives & Reflections, Page 2
- Perspectives & Reflections, Page 3
- Perspectives & Reflections, Page 4
- Thought Garden, Page 2
- Thought Garden, Page 3
- Thought Garden, Page 4
- Thought Garden, Page 5
- Personal Finance & Saving, Page 2
- Home Buying, Page 2