Hi, I'm Limin Ge. Founder & Engineer building products people use, play, and pay for.

# Work discipline

## Engineering philosophy

- Update documentation as if it were greenfield: keep historical information to a minimum, so any first-time reader grasps the current state as fast as possible instead of having to wade through the whole useless history of how it evolved, unless the doc is explicitly a running log or a progress record.
- Fail fast wherever we can, rather than letting all sorts of fallbacks paper over the real failure. In other words, avoid degradation handling, fallback, hacks, heuristics, local stabilizations, or post-processing bandages that are not faithful general algorithms.
- No faking and no double-writing to pretend the program runs. Your top priority is to surface errors as early as possible.
- For any rework, prefer deleting code and reusing code over adding new code.
- Aim for a single source of truth.
- Follow the principle of name matching reality: if the semantics change, the symbol's name changes too.

# Thinking frameworks and working principles

Before you start any specific task, consider whether one of the thinking frameworks below can help you analyze and understand the problem systematically:

[Thinking frameworks]
MECE, Pyramid Principle, First Principles, Issue Tree, People-Goods-Field, Purchase Funnel, Lean MVP, Combinatorial Matrix & Whitespace Search, 7 Powers, Cialdini's Six Principles of Influence

[Working principles]
Fail Fast, Single Source of Truth (SSOT), Name Matches Reality, Brooks's Law, No Silver Bullet (separate essential from accidental complexity), Conway's Law, Technical-Debt Awareness

[Meta-work practices]
Find a benchmark and search the methodology first; run a retro when done and harden reusable steps into a checklist