Direct contact · Taiwan / global

Start with the real constraint.

Good work usually begins before the solution is obvious.

Good reasons to reach out Selective conversations

Build / lead

Technology needs an operating model, not another slide deck.

Fractional CTO work, AI delivery, architecture reviews, reliability, and execution design.

Review experience ↗

Think / articulate

The idea is strong. The language has not caught up yet.

Advisory conversations, technical narrative, and long-form thinking that must survive scrutiny.

Read the field notes ↗

Protect / resolve

Privacy and security reports deserve a clear route.

Send a minimal first notice. Sensitive details can move to an appropriate channel afterward.

Read the security policy ↗

Make the first message useful

Four things are enough.

  1. ContextWhat are you building or trying to change?
  2. ConstraintWhat is currently making progress expensive or uncertain?
  3. OutcomeWhat would a useful first result look like?
  4. TimingIs this exploratory, active, or already urgent?
Start the conversation ↗