At the early-stage startup I was previously part of, I learned more than just how to write code; I learned the structure of how technology functions as a service.
Although my primary focus was on web frontend development, I took responsibility for the core service paths by designing backends and data flows whenever necessary. In particular, I built and operated a pipeline to stably collect, refine, and manage over 1 million fashion product data points using FTP/SFTP and web-based architectures.
Through this experience, I have become convinced that what matters more than any specific language or framework is the ability to understand the overall system flow and responsibility structure.
Currently, I am designing AI-based systems in web environments, focusing on defining structures and control models before execution. Rather than simply adding features, my work is closer to designing state transitions and validation flows.
Starting as a non-major and getting to this point through self-study, I am well aware of the roadblocks and realistic constraints. That is why in my lectures, I focus on "why we design this way" and "how to make decisions" rather than showing off technical skills.
A structure that leaves only the essentials,
instead of increasing complexity.
That is the development philosophy I strive for.