Break your expectation, read real signals, question the unconventional to seek adaptable truth

Coaching Skills

Fact about expectations - Charlie Munger

Social Intelligence

What other pay

How to control and manipulate the decision

Write a ADR

Thinking of others - My missing piece

Kind of people

State a strong argument

System Design Structured

DSA Implementation Structured

Software Engineer Level Growth

How to be a player - Game Theory

How to coach others

Clarity values - what they need in others is what they miss in their childhood.

Signals - how you observe other with facts not assumptions

Control Assumptions - Based on signals, not your expectations

How to detect a sentence is lie or truth

Persuade Skills - Get them to do what you want

Buyers and Sellers - Understand the needs of the other party

Love Advices

How to treat an introverted

Software Engineer Skills

Coding Skills: Latter solution is better than previous solution.
System Design: Design high-level solution + verified each requirement and enhanced questions and facts (metrics, current system).

How to Deal with Uncertain Problems

Telemetry First: Identify service dependencies and understand how services interact.
Explore Service Endpoints: Examine the HTTP and gRPC endpoints exposed by each service.
High-Level Thinking (Intuitive Curiosity): Understand the overall architecture and product vision from Figma designs and system design documents.
Explore the Flow: Trace the end-to-end request flow and identify the core functions within the codebase.
Testing: Run the application and test API endpoints to verify inputs, outputs, and expected behavior.
Coding: Optimize the implementation and perform thorough code reviews.
Monitoring: Add meaningful metrics, logs, and alerts to observe the health and performance of the feature.

Grill weaknesses

Meta thinking first: Draw high-level idea map before doing anything.
Structured Thinking: Order the actions.
Implementation Skills: Understand full flow, not only tickets.
Retain long-term knowledge: store facts, feedback, concepts, active retrieve it in long-term knowledge base.
Present for impact (teach, convince, motivate): stimulate to explain your thinking for other people follow Feynman Technique, 3-sentences rules for other needs, use body language and focus to main point to grab user attention.
Improve quality of outreach, connections: enhance outreach to open communicate with strangers, value connections, and make service for community.

Frame A Decision

Fact is what happening. Proposal comes with trade-offs and reasons.
Needs are about survival. Wants are about desires.
How to learn new thing: See it (mostly 70%). Do it (for high-execution required skills). Feedback it (be corrective feedback with insights)

Nguyễn Đức An

Coaching Skills

Software Engineer Skills

How to Deal with Uncertain Problems

Grill weaknesses

Frame A Decision

Socratic Questions

My expectations 2026

Design Price Tracking Service - Staff Dive Deep Design

1. Requirements

2. High-level Design

3. Knowledges

4. Flow

4.1. Step 1: Scrape flow

4.2. Step 2: Validate + store - anomaly check before TimescaleDB

4.3. Step 3: Alert flow

4.4. Main Flow

5. Number and Metrics

6. Dive Deep Components

6.1. Deep Dive: Anti-Bot Defense, Adaptive Frequency, Parser Resilience

6.2. Trade-offs, Failure modes