Engineering Journal
I approach software through research before implementation. This case study documents how a series of engineering questions shaped my thinking—from software logic and abstraction to architecture, product engineering and ongoing research.
REV A
2026
FIGURE 01
Case Study
Throughout my career, I spent more time understanding software than simply building it. Each project became an experiment to answer a specific engineering question, gradually expanding my perspective from implementation to architecture and product engineering.
This website documents that journey. Rather than presenting a collection of finished projects, it explains why each project existed, what I explored and how those experiences shaped the engineer I am today.
REV A
2026
FIGURE 02
Engineering Log
Every project began with a motivation.
Every answer changed how I approach software engineering.
Engineering Log 01
CSV → JSON Converter
Motivation
I wanted to understand software beyond traditional graphical applications and explore different ways users interact with programs.
Question
Is software fundamentally about user interfaces, or is it primarily about solving problems through logic?
Experiment
Outcome
Software is defined by its logic, correctness and reliability—not by the interface alone.
Engineering Log 02
Node.js Server Library
Motivation
I wanted to understand why frameworks exist instead of simply relying on them.
Question
How are server frameworks designed, and what abstractions make backend development easier?
Experiment
Outcome
Good abstractions simplify recurring engineering problems without hiding how the system works.
Engineering Log 03
Rust Notebook
Motivation
I wanted to combine multiple engineering disciplines into a single software system.
Question
How do operating systems, networking, concurrency and frontend architecture work together in one product?
Experiment
Outcome
Architecture is about coordinating independent systems into one coherent product.
Engineering Log 04
Database Engine (Design Study)
Motivation
I wanted to understand what happens before implementation and learn how senior engineers own complete systems.
Question
How do research, planning and system design influence software before any production code exists?
Experiment
Outcome
Engineering begins long before implementation; research and design determine the quality of the final product.
Engineering Log 05
Symax Product Prototypes
Motivation
I wanted to apply engineering principles in real product development while gradually expanding my responsibilities.
Question
How do engineering decisions evolve as products grow from frontend implementations to complete production systems?
Experiment
Outcome
Building products requires balancing architecture, maintainability, deployment and business constraints together.
Research Notes
Today, my work is driven less by individual technologies and more by researching how software itself can be engineered through reusable systems, thoughtful architecture, and sound design. I am seeking an environment where curiosity, technical rigor, and continuous learning are encouraged, where engineers are empowered to ask why before how, and where building robust, well-engineered systems is valued as much as delivering features.
Research Note 01
Building a modular engineering ecosystem for research, knowledge management, execution and workstation architecture.
Research Note 02
Exploring architecture patterns that make products scalable, maintainable and practical for long-term independent development.
Research Note 03
Researching whether software design itself can evolve into an implementation layer rather than remaining documentation.