SORUNE / SOFTWARE ENGINEER
Product engineering, legacy modernization, reusable runtimes, and engineering infrastructure.
I try to implement what I design, then verify what I implement through tests and operation.
Selected work
Product, runtime, and engineering control plane. Each case study narrows a problem, draws a boundary, and carries it to a state that can be checked.
Product engineering · modernization
A real photo product shaped by the work of untangling legacy code, data contracts, and runtime dependencies.
Current system
In PhotoGram, product, modernization, verification, and delivery share a surface without becoming the same state.
Start with the product that has to work.
Put earlier choices and a new runtime behind one boundary.
Check the state through tests and health signals.
Separate the deployable path from the unknowns that remain.
04 / Relationship map
Product problems become runtime and library boundaries, while Workspace Ops and operations tooling make the conditions of that work explicit.
Experience / journey
Lessons from industrial control and enterprise systems carried into product work, legacy migration, and reusable systems.
A precise state had to be read before the next action.
LabVIEW · sensors · controlPhysical signals became flows people could use in products.
React · Spring · backendClear boundaries made old code changeable one piece at a time.
Gnuboard · MySQL · filesParsers and process made organizational constraints visible in code.
eGov · Excel · OracleRepeated problems became product and library surfaces.
PhotoGram · grid-masonryRuntime and control planes separated relation and ownership.
CharaWeave · Workspace OpsAbout
I separate ownership and scope, leave unknowns visible, and prefer structures that another person can pick up.
Read about the practiceContact
I work on systems that leave behind code, tests, and operational evidence.