Backend & Platform Engineer / Tainan, Taiwan
Reliability signals before the incident.
I read engineering systems as operational surfaces: contracts, event streams, deployment paths, maintenance habits, and the evidence trail a team can use when pressure arrives.
Signal board
Four evidence channels define the work.
CCTS, APSEC 2022, TCSE award
PDAS, payment platform, AKS delivery
HomeLab, iDRAC, internal systems
OSS integrations, localization, docs
Incident memory
Timeline as operational context.
Every system claim is mapped to where it was learned: research, delivery, internal systems, or living infrastructure.
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.
Briefings
Short essays for teams evaluating fit.
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.
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.
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.
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.