Holmes LabAgentic Software Engineering Architect

ENGINEERING JOURNEY / 2000 — PRESENT

Depth in the code.
A wider scope of design.

From a formatting engine to a shared platform. I share six transitions in how I built software, led development and broadened my engineering perspective.

Explore the journey ↓
01Component02Device03System04Product family05Engineering ecosystem

1991 / BEFORE THE PROFESSION

Still living the dream that became my profession.

In 1991, watching Terminator 2 as a middle-school student inspired me to become a software engineer. I heard that C had been used in its remarkable graphics. Wanting to create something myself, I began learning the language.

That dream became my profession. Since 2000, I have turned ideas into software across applications, embedded systems, medical devices and product platforms. I still get to do the work I once dreamed of doing.

Now, the way we build software is changing profoundly. Alongside writing code ourselves, we are entering an era of designing, implementing and verifying software with AI agents.

As a student, the possibilities of computers drew me to C. Today, the possibilities of AI have me learning and building again. I am bringing my experience in architecture, product development and team leadership into this new way of working: Agentic Engineering.

Having found the profession I dreamed of, I am now taking on the challenge of shaping what it becomes next.

A personal recollection · Professional career begins in 2000

01 / THE TECHNICAL THROUGHLINE

Six transitions. Four perspectives.

Choose a chapter to read the work behind it.

A thematic map, not a proficiency chart. Equal-width chapters are not proportional to duration; connections show related experience, not continuous tool usage. Blank cells mean no example is highlighted.

CHAPTER 01

Building tools for people

From a character on a page to a model of an idea.

01Problem & constraints
I built software for editing documents, searching knowledge and representing ideas and business structures on screen.
02Responsibility
I developed a children’s word processor formatting engine and customized its GUI; co-developed MindMapper 3.0 and a supply network planning modeler. Later designed and implemented an old-document database and search web server.
03Engineering approach
I worked across C/C++ desktop applications, Java/JSP and relational databases, implementing document processing, interfaces, storage and retrieval.
04Application context
SimTech Systems: Jan 2000–Apr 2001. Palman Systems: May 2001–Jul 2002. Work included a word processor, MindMapper, an ETRI planning modeler and historical-document computerization.
  • C/C++
  • MFC
  • Java / JSP
  • Oracle / MySQL

HOW I CONNECT THE EXPERIENCE

Building user-facing capabilities drew my attention to the operating systems and hardware underneath them.

CHAPTER 02

Working at the hardware–OS boundary

From board signals to kernels and streaming paths.

01Problem & constraints
I developed an embedded Linux PVR set-top box, working on board bring-up and audio/video data paths.
02Responsibility
I ported the Linux kernel, customized and optimized A/V drivers, and developed a bootloader and firmware-upgrade interface. Co-designed and implemented dual-OS/processor IPC and streaming for a prototype.
03Engineering approach
I used JTAG to debug device control and data paths, connecting kernel, drivers and IPC. Development used C/C++ and PowerPC assembly.
04Application context
DGStation: Aug 2002–May 2003. Embedded Linux PVR development and dual-OS/processor prototyping.
  • Linux
  • C/C++
  • PowerPC Assembly
  • IPC
  • JTAG

HOW I CONNECT THE EXPERIENCE

I carried this experience across software and hardware boundaries into imaging systems and hardware interface design.

CHAPTER 03

Making products work in the field

Imaging control, performance, production and service.

01Problem & constraints
I improved ultrasound imaging control, configuration and a framework running on low-performance CPUs, alongside diagnostics for production and service.
02Responsibility
I served as technical lead for imaging control/configuration and software project leader for ACUSON X300 v4.0, contributing to multiple ultrasound products.
03Engineering approach
I improved the Common Imaging Architecture for constrained CPUs. I built diagnostics, production utilities and automated self-diagnostic/production tests so products could be checked beyond development, in manufacturing and service. I worked with manufacturing and engineering teams on deployment and stabilization.
04Application context
Siemens Healthcare Ultrasound: Jul 2003–Sep 2009. Participated in SONOLINE G40, ACUSON X300/X150 and SONOVISTA FX; supported the Korean manufacturing test environment.
  • C/C++
  • SSE
  • x86 Assembly
  • Python
  • Imaging control

HOW I CONNECT THE EXPERIENCE

Working on production, diagnostics and service broadened my perspective from individual features to system structure and testability.

CHAPTER 04

Designing the whole system

Making testability part of the structure.

01Problem & constraints
I designed software connecting ultrasound imaging control, back-end processing and hardware interfaces.
02Responsibility
I was software architect for H60 and PT60A and software project lead for H60. Immediately beforehand, I designed a unit-testing framework for embedded Linux TV software.
03Engineering approach
I designed and implemented object-oriented architecture and frameworks using .NET and native C++. I treated testability and serviceability as architectural requirements, applying event-driven and data-centric structure.
04Application context
Samsung SDS freelance: Feb–Mar 2010, TV unit-testing framework. Samsung Electronics: Apr 2010–Aug 2013, H60/PT60A architecture and development.
  • C++
  • .NET
  • C#
  • C++/CLI
  • Event-driven architecture
  • Data-centric architecture

HOW I CONNECT THE EXPERIENCE

I extended what I learned about structure and verification within one system to commonality and variation across entire product families.

CHAPTER 05

Designing platforms for product families

Connecting commonality, variation, generations and teams.

01Problem & constraints
I developed shared software platforms across ultrasound products and generations, using SPLE to address common foundations and product-specific variation.
02Responsibility
I led software strategy and execution as ultrasound software architect and SPLE platform development head from August 2013 to April 2026. Across platform and system software teams and the Platform Lab, I connected the shared platform, One Branch and unified UX to commercial delivery.
03Engineering approach
I set a direction that integrated product-specific development through a shared platform and One Branch. I planned UX unification within that strategy. From the perspective of hardware control in software, I led the shift to integrated hardware design with a shared superset and product-specific variants. I carried architecture, code integration and Agile collaboration into commercial products.
04Application context
Samsung Electronics and Samsung Medison. With my teams, I carried the shared platform across the HS60, V8 and Z20/R20 product families. Platform Lab head and deputy S/W R&D group head: Dec 2024–Apr 2026.
  • SPLE
  • Software architecture
  • Platform engineering
  • Agile

HOW I CONNECT THE EXPERIENCE

I now apply what I learned about shared technical foundations and collaboration to AI infrastructure and ecosystems across the organization.

CHAPTER 06

Expanding how engineering gets done

Connecting AI infrastructure and ecosystems to real work.

01Problem & constraints
I focus on secure, scalable internal AI infrastructure and ecosystems supporting enterprise-wide transformation in medical equipment.
02Responsibility
I lead the AX Development Part at Samsung Medison. Agentic Software Engineering Architect describes the professional practice I am developing.
03Engineering approach
I architect and build internal infrastructure and ecosystems through AI Platform Engineering. Internal implementation details and operational results are not disclosed on this page.
04Application context
Samsung Medison: led the AX Development Group from April 2026; the organization was renamed AX Development Part on 2026-10-16. Current role: Head of AX Development Part. Here I describe the development direction and responsibilities I currently lead.
  • AI Platform Engineering
  • AI infrastructure
  • AX

HOW I CONNECT THE EXPERIENCE

I bring implementation, product lifecycle, shared platforms and organizational leadership together in my current work. Below, I share my personal engineering projects separately.

2009 / RESEARCH & IMPLEMENTATION

Designing reliability into the structure.

Beyond software that works, I explored structures that can recover when something goes wrong. I separated control flow from data flow and designed and implemented C++ frameworks for specification-driven state machines, a data repository, event handling and application-level checkpointing.

Conceptual overview of the research
  1. Specify behavior
  2. Coordinate control with FSMs
  3. Save data and state
  4. Recover an earlier state

I modeled playback, recording and channel changes in a simplified PVR example, then forced failures during event handling to verify recovery to an earlier state.

Research scope: single-threaded execution and simple rollback. Recovery accounting for relationships between events and multithreaded support remained future work.

HOW I CONNECT THE EXPERIENCE

An interest in specifying behavior, separating complexity and designing for failure connects this research to product-line platforms and today’s Agentic Engineering. My current work seeks to connect requirements to code through evidence of change and to verify the work of AI agents.

Master of Engineering thesis · Ajou University · Submitted November 2009
A Design and Implementation of Fault Recoverable Framework for Embedded Software

LEADERSHIP / PRACTICE → PRODUCTS → GROWTH

Changing how we build. Creating a foundation for growth.

I looked beyond the next product to a development system that could support generations of products. I set the direction for a shared SPLE platform, One Branch and a unified UX, and led the transition toward integrated hardware and variant design alongside Agile adoption. I connected architecture, development projects and organizational practice to commercial delivery.

  1. Putting Agile into practice

    We expanded from Daily Scrum to sprint planning and reviews, then widened participation in those reviews. Through trial and adjustment, I helped build a practice where development and verification teams could share feedback, rather than simply follow a prescribed format.

  2. From SPLE and One Branch to shipped products

    I led platform development that replaced product-by-product code copying with designed commonality and variability. Integrating variant changes into a shared base and strengthening a One Branch strategy allowed engineering investment to benefit multiple products. I saw the need to manage product differences as deliberately as shared capabilities, and began implementing Feature Configuration in 2013. I planned UX unification as part of the One Branch strategy, extending beyond shared code into One UX in 2018 and leading its application in commercial products. From the perspective of hardware control in software, I also led the transition from fragmented product-specific hardware designs to an integrated superset-and-variant design approach, aligning hardware development with the shared-platform strategy. Products had different target specifications and commercialization schedules, making it difficult to sustain a shared platform and One Branch strategy. Despite early concerns about efficiency and feasibility, I led individual product delivery alongside the development of our shared engineering system. With my colleagues, I carried the strategy through to commercial products, improving development efficiency and extending accumulated technology across product families to contribute to company growth and business results.

  3. Reviewing requirements together

    I wanted quality and implementation decisions to happen earlier, so we renewed joint requirements and specification reviews across planning, design, development, quality and service. Cross-review during design and verification alongside development supported Shift Left Testing and earlier collaboration on quality.

  4. Connecting engineering to business growth

    The platform development and commercialization I led contributed to the technical foundation of product competitiveness as Samsung Medison returned to profitability and entered a period of growth. In my public reflection in April 2026, I described observing improvements in field-quality indicators alongside revenue growth as the platform advanced. Leaders who supported the strategy and colleagues who worked through its challenges made this journey possible. Business outcomes were shared achievements across product planning, hardware, imaging, software, quality, sales and other teams.

I revisit the experience I shared in my June 2024 presentation and public reflection of April 12, 2026: the direction I set, the execution I led, and the changes my colleagues and I made together across teams.

Read my April 2026 reflection on LinkedIn ↗

02 / PERSONAL ENGINEERING PRACTICE

Experience, put
into practice.

I design and develop Holmes-Kit, Jarvis and Holmes Lab as personal projects. I introduce them separately to show how my professional experience informs my current practice.

I have brought together my career, personal recollections, June 2024 presentation and April 2026 public reflection. The chapters follow changes in my engineering perspective; individual role dates appear in the details. I describe the decisions I led and the products my colleagues and I brought to market.

Head of AX Development Part · Samsung MedisonSince October 16, 2026

Discuss an engineering question ↗