Editor's Introduction
A full editorial profile: history, essays, engineering path, and the systems mindset behind this journal.
Editor's Dossier
From a 14-year-old writing math and science essays to shipping systems in robotics, automotive, and industrial vision.
This page is intentionally dense. It combines narrative and factual structure so the story is not only readable, but also verifiable. The backbone comes from CV data and past records: Pol Math School essay work, 42 learning path, SEA:ME, Bosch, and Pickit 3D.
Started coding
Age 14
While writing math/science essays.
Core training
42 Seoul
Peer learning, C, systems, project rigor.
Mobility track
SEA:ME
Software engineering for automotive ecosystems.
Recent focus
Pickit 3D
Industrial robotic picking, Aug 2025 - Mar 2026.
Editorial Position
Stress reveals structure.
Elegant systems in ideal conditions are easy to produce. Durable systems under noise, delay, hardware limits, and real operators are not.
Every major section below cross-links narrative and data. If a statement matters, it appears as a timeline item, a row in a table, or an expandable detail block.
Working language and tools
Technical stack used across robotics, mobility, and product engineering.
C, C++, Python, TypeScript, Assembly, React, ROS 1/2, Docker, Git, GitHub, Figma, Qt, Flutter, and CARLA are used as tools, not identity markers. The constant is maintaining system shape under real constraints.
Languages: Korean (native), English (professional).
Stack by domain
- Robotics and vision: C++, Python, ROS, deployment debugging.
- Automotive and HMI: TypeScript, React, V2X interfaces, safety-first UX.
- Embedded and prototyping: Qt, Flutter, Raspberry Pi, Arduino.
- Workflow and delivery: Docker, GitHub, CI habits, structured test loops.
Origin Story
I didn't start by building systems.
I started by trying to explain them.
Age 14 · Pol Math School
Writing math and science essays forced me to:
- Define assumptions explicitly
- Prove relationships step by step
- Test logic against edge cases
That habit stayed. Today, I still treat systems the same way:
define → model → break → revise
The difference now: I pressure-test against reality instead of paper.
| Essay / Study Topic | Domain | Method | Became this habit |
|---|---|---|---|
| Coordinate calculation from distances between three points in space | Geometry / computation | Rigorous derivation → verification against test cases | Always validate models against edge cases before trusting them. |
| DNA replication via Scratch | Biology + simulation | Break complex phenomenon into explicit rules and test each | Decompose systems into verifiable components. |
| Regular pentagon in complex plane and equation roots | Pure mathematics | Symbolic proof + explicit notation of all assumptions | Write systems as if someone must prove them correct. Invisible assumptions kill systems. |
| Darwin's evolution via EvoDots simulation | Scientific reasoning + tooling | Use simulation to test competing theories; observe which survives | Pressure-test designs. Elegance that fails under pressure is not elegant. |
Timeline
Each transition was intentional. Each one closed a gap.
Sep 2020 - Aug 2022
Open
42 Seoul: common core and systems discipline
Sep 2020 - Aug 2022
Open
Why here: Needed foundational rigor in systems thinking and C before anything else mattered.
- Built strong collaboration through peer evaluation, diverse team projects, and hackathon delivery cycles.
- Strengthened C, debugging, and memory behavior through repeated team-based implementation.
- Developed execution habit: test early, share feedback quickly, iterate as a team.
Jul 2023 - Jun 2024
Open
SEA:ME in Wolfsburg: bridging software and physical systems
Jul 2023 - Jun 2024
Open
Why here: Moved from pure software to systems where code meets hardware, operators, and real-world constraints.
- Studied software engineering in automotive and mobility contexts.
- Connected embedded, communication, and product-level decisions in one workflow.
- First time managing tradeoffs between elegance and industrial feasibility.
Jun 2024 - Nov 2024
Open
Robert Bosch: safety-critical systems in production
Jun 2024 - Nov 2024
Open
Why here: Needed to test design philosophy against safety-critical requirements where failures have real consequences.
- Built V2X demonstrator for safety-critical automotive scenarios.
- Integrated across communication, software, and HMI layers.
- Learned what "shipped and reliable" really means in automotive.
Aug 2025 - Mar 2026
Open
Pickit 3D: operationalizing systems under real noise
Aug 2025 - Mar 2026
Open
Why here: Final test: does the philosophy hold when the system must survive operator error, WiFi dropouts, and hardware variability all at once?
- Worked on 3D vision-powered robotic picking in production settings.
- Diagnosed real deployment failures (WebSocket instability, node desynchronization, log pipeline timezone normalization).
- Reduced on-site debugging cycles and prevented recurrence via validation checks.
Interactive CV Map
Evidence density: problem → solution → impact.
| Domain | Problem diagnosed | Technical approach | Result |
|---|---|---|---|
| Industrial robotics | ROS nodes desynchronizing under packet loss; vision pipeline failing on noisy WiFi | Exponential backoff, heartbeat validation, log pipeline with timezone-aware normalization | Reduced on-site debugging cycles; prevented recurrence via validation checks |
| Automotive systems | V2X communication latency tolerance unclear; HMI interaction patterns untested for safety scenarios | React HMI with explicit state machine for safety transitions; communication layer with deterministic delivery guarantees | Demonstrator delivered; ready for OEM validation |
| Applied AI and simulation | CNN lane detection overfitting to CARLA weather conditions; poor transfer to real camera data | Domain randomization in simulation; multi-condition training pipeline | Model generalization improved; foundation for real-world deployment |
| Full-stack/product engineering | Editorial content + deployment infrastructure decoupled; hard to maintain and iterate | Code-content co-location in TSX; per-page media folders; dynamic transpilation with path rewriting | Editorial + engineering workflows unified; this journal is the artifact |
Education and Credentials
Parallel tracks, formal degrees, and practical certifications.
Degree and training timeline
| Period | Program | Result |
|---|---|---|
| 2026 - ongoing | B.Sc. Mechatronics | In progress |
| 2024 - 2025 | B.Sc. Artificial Intelligence | GPA 3.44/4.5 |
| 2019 - 2020 | B.Sc. Computer Engineering | GPA 4.24/4.5 |
| 2019 - 2022 | B.Sc. Business Administration | GPA 3.77/4.5 |
| 2020 - 2022 | 42 Seoul Common Core | Completed |
| 2023 - 2025 | 42 Wolfsburg Advanced Core | Transferred and continued |
Selected certifications
| Year | Credential | Issuer / level |
|---|---|---|
| 2025 | Network management certification (listed in current CV) | Professional qualification |
| 2022 | TOEIC Speaking 160 | Advanced Low |
| 2021 | TOEIC 860 | Language certification |
| 2020 | Engineer Information Processing | HRD Korea |
| 2020 | Craftsman Electronic Apparatus | HRD Korea |
| 2019 | Computer Specialist in Spreadsheet and Database Level I | KCCI |
Curriculum Vitae
PDF for formal use, this page for engineering context.
The two CV files remain the official summary artifacts. This editor page adds missing context: decision style, system constraints, and evidence across projects and domains.
PDF / Industry
Industrial CV
Product engineering, robotics deployment, software integration, and operations.
PDF / Academic
Academic CV
Graduate applications, research trajectory, and formal educational history.
What this journal tracks
The real engineering: what breaks, why it breaks, and what we learn.
- ▸ Invisible assumptionsHow systems pass all tests, then fail in production the moment an assumption was violated.
- ▸ Operator realityHow software and hardware interact under human error, fatigue, and real-world constraints that designers didn't anticipate.
- ▸ Interface clarityHow systems die because teams could not see the same problem. Clarity in interface design prevents that death.
- ▸ Decisions and timeHow architecture choices made under pressure look very different after 18 months of operation and three production incidents.