Backend & Platform Engineer

Research ideas forged into deployable systems.

Backend and platform engineer connecting event-driven research, production delivery, and home-lab operations.

Workbench

Projects grouped by what they prove.

Build pipeline

A repeatable path from ambiguity to operable software.

01

Observe

Find where runtime behavior and team expectations diverge.

02

Model

Turn flows into contracts, event paths, deployment notes, or testable boundaries.

03

Build

Ship the smallest durable system that reduces operational uncertainty.

04

Harden

Document, monitor, and remove friction before complexity compounds.

Material history

The craft came from multiple pressure types.

Internal systems under real business constraints

Ming-Chyuan MIS work creates a long-running baseline: software has to survive legacy systems, manufacturing workflows, and maintenance pressure.

Computer science training at NTOU

B.S. and M.S. work converge on service-oriented architecture, event-driven testing, and maintainability under research constraints.

CCTS and SOSELab research line

CCTS turns consumer-driven contracts, event logs, and state models into a composite test service for event-driven microservices.

ITRI PDAS delivery work

Personal-data authorization and valuation/payment platform work spans logging, payment, blockchain, CI/CD, fintech integration, and AKS delivery.

Home-lab and public collaboration

Self-hosted systems, server automation, and public PRs keep the engineering habit grounded in operational feedback.

Shop notes

What the system should leave behind.

Static JSON APIs

Profile, projects, metrics, insights, styles, search, feed, OpenAPI.

all variants

Command palette

Keyboard-accessible search over headings, insights, projects, and APIs.

all variants

Live GitHub fetch

Client fetches public GitHub profile and falls back gracefully.

progressive enhancement

Chart layer

Impact bars, timeline, article taxonomy, and role-fit matrices.

all variants

Documentation pack

Design rationale, technical notes, Mermaid diagrams, branch/deployment instructions.

ten variants

Contracts Are Only Useful When They Meet Runtime Evidence

CCTS matters because it connects contract definitions with event-log paths and state-model assertions, closing the gap between interface agreement and actual behavior.

6 min read

Delivery Documentation Is Architecture Work

The PDAS work shows why deployment, CI/CD notes, infrastructure constraints, and customer handoff are not afterthoughts; they decide whether the system can be trusted.

5 min read

Give me the messy system and the real constraints.

Start a conversation

Portfolio intelligence layer

Research evidence, APIs, charts, and blog-grade operating notes.

This shared layer turns every variant into a richer portfolio surface: API endpoints, command search, live GitHub enrichment, article cards, timeline context, and machine-readable data.

Live enhancement

GitHub public API slot

The client can fetch current public profile data without requiring secrets. If the network fails, static evidence remains complete.

Static fallback 127 repositories / 23 merged PRs
Capability matrix

Feature coverage

Static JSON APIs all variants
Command palette all variants
Live GitHub fetch progressive enhancement
Chart layer all variants
Documentation pack ten variants
Impact chart

Proof distribution

92 CCTS, APSEC 2022, TCSE award
86 PDAS, payment platform, AKS delivery
88 HomeLab, iDRAC, internal systems
76 OSS integrations, localization, docs
Timeline

Context map

Internal systems under real business constraints

Ming-Chyuan MIS work creates a long-running baseline: software has to survive legacy systems, manufacturing workflows, and maintenance pressure.

Computer science training at NTOU

B.S. and M.S. work converge on service-oriented architecture, event-driven testing, and maintainability under research constraints.

CCTS and SOSELab research line

CCTS turns consumer-driven contracts, event logs, and state models into a composite test service for event-driven microservices.

ITRI PDAS delivery work

Personal-data authorization and valuation/payment platform work spans logging, payment, blockchain, CI/CD, fintech integration, and AKS delivery.

Home-lab and public collaboration

Self-hosted systems, server automation, and public PRs keep the engineering habit grounded in operational feedback.

Engineering journal

Blog-grade essays distilled into portfolio proof.

Research / 6 min read

Contracts Are Only Useful When They Meet Runtime Evidence

CCTS matters because it connects contract definitions with event-log paths and state-model assertions, closing the gap between interface agreement and actual behavior.

CCTScontract testingevent-driven systems
Delivery / 5 min read

Delivery Documentation Is Architecture Work

The PDAS work shows why deployment, CI/CD notes, infrastructure constraints, and customer handoff are not afterthoughts; they decide whether the system can be trusted.

PDASAKSCI/CD
Operations / 4 min read

A Home-lab Keeps Platform Taste Honest

Running storage, DNS, monitoring, media, albums, and automation changes how architecture feels: failures become personal, and clarity becomes operational leverage.

HomeLabDockeroperations
Collaboration / 4 min read

Small Open-source PRs Show How Someone Enters a Codebase

Integration, localization, and documentation fixes reveal a practical collaboration style: learn the boundary, reduce friction, and leave a clearer path behind.

OSSintegrationdocumentation
Switch design system
01 Noir Systems Dossier A high-contrast operational dossier for backend/platform credibility. 02 Linen Editorial Portfolio A quiet editorial page for maintainability, reliability, and human-readable engineering. 03 Glass Runtime Surface A translucent runtime dashboard for research, platform delivery, and live-link exploration. 04 Ink Specification Sheet A brutal specification sheet for teams that value directness and strong information hierarchy. 05 Dusk Reliability Narrative A dark narrative surface for systems that keep working after the demo. 06 Atlas Evidence Map A map-like editorial layout that presents identity through research, delivery, operations, and collaboration routes. 07 Signal Operations Desk A command-center portfolio focused on observability, incident thinking, and reliability signals. 08 Forge Engineering Workshop A workshop-style portfolio that shows how research ideas become deployable systems. Current 09 Observatory Analytics Lab A data-rich analytics page for publications, contributions, systems, and role-fit evidence. 10 Archive Knowledge Journal A premium blog/editorial archive for long-form engineering narrative and proof-backed writing. ☰ Open the full gallery Compare palettes, theses, and interaction effects side by side.
Search portfolio intelligence
Portfolio API console
{
  "ready": true,
  "hint": "Choose an endpoint to preview JSON."
}