Learning the Strict Language of Code: No Subject Omissions Allowed!

From Distant Memories of HTML to a Reunion with Python

My first encounter with code goes quite far back. It started in an after-school computer class in elementary school where I first touched HTML. Back then, I had no clue it would become such a powerful tool that changes the world. It remained buried in my memory as just a fascinating game of making text appear on a screen and changing its colors.

Years later, just before joining a startup, I got a taste of 'Python.' As a strategy consultant accustomed to handling countless formulas and functions in Excel, Python felt somewhat unfamiliar yet strangely recognizable. Since it shared a logical structure similar to Excel formulas, code didn't feel like an "alien language" to me. Instead, I calmly accepted it, thinking, "Ah, this is essentially just another sophisticated formula."

However, through the rigorous process of a startup bootcamp and an AI bootcamp, I realized that code is much more than just a 'formula.' It was a 'language of absolute specificity' where no omissions are allowed—a stark contrast to human conversation.

Excel is Interior Design; Coding is Laying the Foundation

When handling Excel as a strategist, I was more like an 'interior designer' choosing wallpapers and arranging furniture within a pre-built house. Excel provides a user-friendly UI where all the tools and materials are already prepared. My job was simply to combine those materials to extract the desired results. Since the results were instantly visible in each cell, trial and error felt intuitive.

Coding, however, was different. It wasn't interior design; it was 'laying the foundation'—drafting blueprints on a wasteland and digging the first hole. Unlike Excel, where the environment is fully set up, I had to decide for myself which materials to use, how to withstand the load, and where to place the pipes.

I quickly learned that if you start coding recklessly, it becomes nearly impossible to fix the structure halfway through. Just as a house with poorly set pillars will eventually collapse no matter how flashy the interior is, I experienced firsthand that if the initial design and foundation of code aren't solid, it returns as uncontrollable technical debt. That solitary work of filling a black screen with text was a noble process of creating the essential structure hidden behind a flashy UI.

The Language of Context vs. The Language of Specificity

Human conversation is an art of 'context.' When we say, "I'm heading out," the listener understands that I'm stepping out the door to run an errand without needing further details. We can communicate even when subjects and objects are omitted because we share a common context.

Code, however, tolerates no such omissions. To give the command "Go out," you must specify without fail: Who is going, Where they are going, How they are going, and for What purpose. A single minor omission creates a system-wide 'error.'

This characteristic of code refined my way of thinking to be more precise. Setting a logical hypothesis as a strategist and implementing that hypothesis into flawless code as a developer required a different dimension of precision. The honesty of code, where even simple things must be explicitly addressed, became my most reliable standard when building services as a solo builder.

Entrepreneur and Architect: Problem-Solving Beyond Tools

At the startup bootcamp, I learned how to quickly deploy an MVP (Minimum Viable Product) and read the minds of users. I learned the flexibility to 'pivot' while receiving sharp feedback from successful entrepreneurs and investors. Conversely, at the AI bootcamp, I developed the fundamental ability to use technology as a tool to solve problems.

This is where I discovered a crucial connection: the mindset of a strategy consultant and that of a developer are essentially aligned. Even if the tools and materials for building a house are the same, the result varies drastically depending on the architect's vision. Code is the same. Whether it's Python or JavaScript, they are just tools. What makes the real difference is the architectural philosophy of "what problem to solve and from what perspective."

The insight I've built as a strategist allows me to look beyond mere functional implementation and center the service's purpose and user value. It's not technology for technology's sake, but technology for the sake of solving problems. That is my stance toward code.

Conclusion: Designing the World with My Own Language

I am still most comfortable with Python, and I spend my days struggling with unfamiliar frontend languages for web deployment. Sometimes it's frustrating that results aren't instantly visible like in Excel, and I rack my brain over the specificity of code that cannot be omitted.

Yet, I enjoy this process. Code has gifted me a 'new language' to observe and redefine the world. As a non-major, the process of expanding my technical repertoire one by one is slow but solid. My journey—laying the ground with pure HTML, finding efficiency with 11ty, and now moving toward React and advanced backend courses—is the process of building a robust house filled with my own philosophy.

Analyzing the world through a strategist's eyes and building the alternative with a developer's hands. The new language of code has transformed me from a mere analyst into a 'Builder' who directly designs and constructs the world. Though I sometimes feel anxious about unproven growth, I believe that these specific lines of language I write one by one will eventually culminate into a magnificent architecture that didn't exist before.