Projects & operationsTaipei, Taiwan

I bring structure to
complicated work.

From technical projects to client delivery and business investigations, I make the problem clear, the evidence useful and the next step visible.

View selected work
01 / Selected work

The work, in context.

What needed to happen.
My part. What came of it.

Client engagement

Onsite delivery in Taiwan

Physical service work in Taiwan, connected to an overseas team through clear communication and remote engineering guidance.

Outcome / current state

Two paid engagements completed; a 5/5 review on the screen-replacement job.

Completed2024–2025Read case

Contract role · Lenovo ISG

Linux server validation

Hands-on server qualification, issue documentation and follow-up across engineering teams and operating-system vendors.

Outcome / current state

Reviewable validation records, defect handoffs and visible next actions.

CompletedMay–August 2026Read case

Business investigation

ServerQual

An investigation into whether recurring server qualification problems could support an independent service.

Outcome / current state

Stopped V1 when the evidence did not justify continuing the service concept.

ClosedAugust–September 2026Read case

Independent technical projects

FPGA / Linux integration

Tracing data-transfer failures across hardware and software, then checking that the corrected system behaves as expected.

Outcome / current state

Stable 1 Gbps Ethernet reception; sustained PCIe DMA above 800 MB/s in the recorded setup.

Recorded workProject archiveRead case

Client work, employment and independent projects, with their scope made explicit.

View all work
02 / How I operate

Enough structure
to move the work forward.

Three habits across different kinds of work.

  1. 01

    Start with reality.

    Understand the situation, the people and the constraints. Make the expected result specific enough to check.

    In practice: ServerQual
  2. 02

    Make evidence usable.

    Keep the conditions, observations and conclusions connected. Give the next person enough context to review the result.

    In practice: validation
  3. 03

    Close the loop.

    Keep blockers, owners and next actions visible. Confirm the final state, or make a clear decision to stop.

    In practice: client delivery
03 / Evidence

Results need context.

A few concrete outcomes.
Each belongs to a specific piece of work.

Client feedback / February 2025

5/5

Clear communication.
Accountability for the outcome.

The client’s review of the screen-replacement engagement highlighted communication, professionalism, accountability and ease of coordination.

Paraphrased Upwork feedback from one completed engagement.

Read the delivery case
System integration

Stable 1 Gbps reception

Ethernet receive behavior restored after tracing frame-start corruption to interface timing.

Read the technical record
Performance benchmark

0.28 to 1.3 GFLOP/s

Approximately 4.6× in a recorded C++ sparse matrix-vector test. The improvement is specific to that setup.

See the benchmark context
Business investigation

A documented stop decision

ServerQual V1 closed when the available evidence did not justify continuing the original service concept.

Read the decision
04 / Current focus

Where I’m taking
the work next.

Technical operations and project execution: connecting the details of the work with the people who need to act.

I’m interested in work spanning engineering, customers and vendors, where clear scope, useful evidence and reliable follow-through matter. I’m also developing my practice in workflow and business analysis.

I’m based in Taipei and work in Mandarin and English.

More about Ian
05 / Field Notes

Notes from the work.

Practical records of methods,
questions and decisions.

One collection for operating notes and project reflections.

All Field Notes
06 / Contact

What are you
working through?

For a project, a work opportunity or a conversation about these cases, tell me what needs to happen and where the work is getting stuck.

Contact me on LinkedIn