I am a product-oriented engineer who builds software as a complete, shippable system rather than as isolated features. My strength lies in turning fragmented goals, unfinished implementations, broken builds, and unclear delivery paths into coherent products that can actually be used, distributed, and maintained.
My work is grounded in C++, Qt, and QML, but my role extends beyond implementation alone. I think in terms of product structure, user experience, interface coherence, build reliability, packaging, deployment, and the overall quality of delivery. I care not only about whether something works, but whether it works as part of a complete product.
Over time, I have taken on projects that were partially built, difficult to maintain, or stuck in non-buildable or non-deployable states, and reorganized them into distributable software. This has included resolving layout and responsiveness issues, fixing broken UI behavior, restructuring project architecture, documenting codebases, clarifying modification points, and automating repetitive build and deployment workflows through scripting.
Alongside engineering, I work naturally across the surrounding layers that make products real. I write and refine README files, installation guides, internal technical documentation, UI copy, and configuration language. I identify usability confusion points, document reproduction steps, and improve the clarity of communication between the product, its operators, and its users. I do not see these as peripheral tasks; they are part of product quality.
I also founded iisacc, where I oversee the full product cycle from planning and development to design, distribution, sales, and customer support. Through this work, I have built and maintained products, a Svelte-based brand website, product pages, store architecture, payment flows, and SEO structures while developing the product messaging and tone that support both usability and brand identity. This experience has strengthened my sense that software quality is inseparable from the systems around it.
What distinguishes my approach is that I do not treat engineering, design, and delivery as separate concerns. When I implement a feature, I think about its place in the overall product structure, how it will be experienced by the user, how it will be shipped, and how it will be maintained over time. I am most effective in roles where software is treated not merely as code to be written, but as a product system to be shaped, completed, and brought into the world responsibly.

Work Terms

I'm always at home. The room and the body are one. You can think that you can actually work at any time because you don't have much sleep time. However, since I live in Korea, you have to consider the time difference.I'm always at home. The room and the body are one. You can think that you can actually work at any time because you don't have much sleep time. However, since I live in Korea, you have to consider the time difference.I'm always at home. The room and the body are one. You can think that you can actually work at any time because you don't have much sleep time. However, since I live in Korea, you have to consider the time difference.