DEV Community

Flovian Atieno
Flovian Atieno

Posted on

What Really Happens When You Hit "Run"? Lessons from the Compilers & Interpreters Mini Conference

As developers, we spend countless hours writing code. We type, save, hit Run, and expect our programs to work. But have you ever stopped to ask yourself:

What actually happens between pressing "Run" and seeing your program execute?
Enter fullscreen mode Exit fullscreen mode

That question was at the heart of the Compilers & Interpreters Mini Conference hosted at Zone01 Kisumu, where I had the opportunity to co-host alongside my fellow apprentice.

One of the biggest challenges for many developers especially those starting their journey is that we often learn how to write code before understanding how the computer understands it. This gap can make debugging, optimizing, and even learning new programming languages more difficult.

Understanding the Journey of Your Code

The conference explored the fascinating journey source code takes before it becomes a running application.

We discussed:

The difference between compilers and interpreters

How programming languages are translated into machine understandable instructions

The role of lexers, parsers, and Abstract Syntax Trees (ASTs)

The compilation pipeline and code generation

Why modern programming languages often combine compilation and interpretation
Enter fullscreen mode Exit fullscreen mode

These concepts may sound theoretical, but they influence the performance, portability, and developer experience of every language we use.

Learning by Building

Theory alone isn't enough.

The highlight of the event was a hands-on workshop where participants built a simple interpreter and a simple compiler. Breaking down these systems into smaller components made concepts that once seemed intimidating much easier to understand.

There's something incredibly satisfying about seeing how a language processes text, understands syntax, and eventually executes instructions.

Why This Matters

Understanding what happens under the hood changes the way you think about software development.

Instead of treating programming languages as black boxes, you begin to appreciate:

Why syntax errors occur

How programming languages detect mistakes

Why some languages execute faster than others

How programming tools are built
Enter fullscreen mode Exit fullscreen mode

These are fundamentals that make us not just better programmers, but better problem solvers.

Top comments (0)