Talk
Beginner
First Talk

Under the Hood: How One Integer Powers Terminals, Servers, and Smartwatches

Approved

Session Description

What if I told you that a single integer is responsible for everything from a terminal displaying text your smartwatches tracking steps, or your browser loading this very page!

In 1970s, Unix engineers made a bet. What if we treated everything; keyboards, network connections, even hardware sensors as something you could simply read from and write from. They called it a file descriptor. Fifty or years later, this "temporary hack" hasn't just survived, it has grown and blossomed into one of the most successful abstractions in computing history.

Here's the wild part:

When you type in a terminal, every keypress travels through at least four file descriptors before bash even sees it!

localhost:3000 isn't magic it's just file descriptor #7 (or whatever number the kernel happened to picked).

A smartwatch reading your heart rate or and a server handling millions of requests use the exact same system calls! Read and Write.

In this talk, we'll explore:

  1. The "aha!" moment: What file descriptors actually are (spoiler: it's beautifully simple)

  2. Live demo of a terminal emulator I built in Rust to expose and explore the pseudo terminal magic underneath

  3. Why the same 5 line code pattern handles a text file, a gigabit network stream, and a temperature sensor

  4. How the "everything is a file" approach made Unix composable, hackable, and ultimately open source friendly.

Target Audience:

  1. Developers at any level who are curious about what happens "under the hood"

  2. Students and independent programmers looking to understand the "why" behind systems design

  3. Anyone who has ever stared at a terminal and thought "wait, how does this work?"

Key Takeaways

Understand what file descriptors are why they're the foundation of all I/O in Unix systems.

Learn how terminals actually work. From keystroke to shell. Understanding PTY master and slave descriptors.

See how the same read()/write() pattern powers everything from local files to network sockets to hardware sensors

We'll learn how to debug common errors like "broken pipe," "too many open files," and blocking I/O issues

Walk away with a mental model that makes programming intuitive from building CLIs, configuring servers, even embedded applications

References

Session Categories

Technology architecture

Reviews

0 %
Approvability
0
Approvals
0
Rejections
0
Not Sure
No reviews yet.