Structure before code, delivery is the goal — from Web to desktop to embedded.
No ambiguous requirements. Think it through before building.
PDCA drives progress, layer by layer.
The real world is a web, not a spreadsheet.
Open-source first, AI-accelerated, choose what fits.
Code is just a byproduct; delivery is the start.
Tools need a business context to create value.
ExploreNo ambiguous requirements. Break it down until it's measurable and verifiable — that's clarity.
Advancing with PDCA: plan first, then execute in stages, check, and adjust — never jump into writing messy code. Decouple only after the structure is clear. Don't cram everything together.
PDCA drives progress. Break down, research, plan, execute, review — layer by layer.
Decouple only after the structure is clear. Don't cram everything together. Reuse everything reusable — extractable modules, styles, components, and workflows are all made reusable when possible.
The real world isn't a 2D table. Data is a web of relationships, not rows and columns.
I consider user needs, deployment paths, maintenance costs, and how tools fit into real workflows — all together. Product plus operations perspective, debugging and iteration discipline, documentation and handoff awareness — these matter more than the code itself.
I often connect APIs, spreadsheets, local files, and prompt systems, turning scattered manual steps into running workflows.
Open-source first, AI-accelerated. Choose what fits best, not what's flashiest.
Research open-source projects first: If a suitable open-source solution exists, I study how others have done it before deciding. When no open-source project exists, research AI solutions: But AI is an accelerator, not a replacement for structural thinking.
Code isn't the only focus: Whether the functionality is correct, stable, and usable matters more than simply piling up code.
Code is just a byproduct. Documentation, deployment, maintenance, and iteration — that's where delivery begins.
If you want to see specific repositories, code walkthroughs, architecture explanations, or a recruiting-focused technical screening version, I can showcase the most relevant code by scenario: growth tools, internal software, automation tools, or multi-platform builds.
Think it, build it
From technology fundamentals to business scenarios — a systematic study of blockchain, stablecoins, RWA, and decentralized finance
Harness Engineering, AI Agent development, Prompt Engineering, and multi-model collaboration — AI is not just a tool, it's a new way of working
From Docker containerization to Cloudflare deployment — building scalable, high-availability cloud infrastructure
Tools need a business context to create value
Explore Investment Framework →
With Jensen Huang at HKUST — I'm behind him.
He stood before me, yet I felt we were no different — just two people on different pages of the same story. He may be the most important person in the world, but his time bank has fewer deposits than mine.