Foundations
CS Foundations
Before you write a single line of application code, it helps enormously to understand the machine underneath it: how a program actually runs, how an operating system juggles thousands of processes, how two computers on opposite sides of the planet exchange data, and what actually happens between typing a URL and seeing a page. This is the layer most self-taught developers skip — and the layer that separates someone who can copy a tutorial from someone who can debug a production incident.
Topic Map
Everything in this module, at a glance
In Depth
Every topic, explained — with real-world industry context
How Computer Programs Work
The code you write is not what the CPU runs. Understanding the journey from source code to executed instructions demystifies almost every "why is this happening" question you'll ever have.
- Source code → compiler/interpreter → machine code
- Compiled languages (C++, Go) vs. interpreted/JIT languages (Python, JavaScript)
- The stack (function calls, local variables) vs. the heap (dynamic memory)
- What actually happens when a program crashes or hangs
Real-World Industry Use Case
When a Node.js server "runs out of memory" in production, the on-call engineer is reasoning directly about heap allocation and garbage collection — the exact model taught here. Compiler design also directly powers tools you already use daily: TypeScript, Babel, and every linter are all programs that read your source code as data.
Computer Architecture & Data Representation
Every value in a computer — text, images, video, this very page — is ultimately just binary. Understanding how data is represented explains behavior that otherwise looks like magic (or bugs).
- CPU, RAM, and storage — and why the speed gap between them matters
- Binary, hexadecimal & how numbers are actually stored
- Bits, bytes, and character encoding (ASCII / UTF-8)
- Why floating-point math is sometimes "wrong" (0.1 + 0.2 problem)
Real-World Industry Use Case
The infamous "0.1 + 0.2 !== 0.3" behavior in JavaScript — and every language using IEEE 754 floats — is a direct, practical consequence of binary floating-point representation, not a bug. Choosing the right cloud instance type (CPU-optimized vs. memory-optimized) at a company like AWS or Google Cloud is a direct application of this hardware knowledge.
Operating Systems
The OS is the software that manages every other piece of software — deciding what runs when, who gets memory, and who can access what.
- Processes & threads — how your computer runs many programs at once
- Memory management & virtual memory
- File systems, permissions & the shell
- System calls — how programs ask the OS for resources
Real-World Industry Use Case
Every "permission denied" error when deploying to a Linux server is the OS enforcing file permissions exactly as taught in this module. Docker — the tool nearly every modern engineering team uses to ship software — is fundamentally a clever use of OS-level process isolation, not a new invention from scratch.
Computer Networking
Nothing you build matters if it can't talk to anything else. Networking is how two independent computers agree on how to exchange data reliably.
- The TCP/IP model — how data actually travels across a network
- The client-server model
- DNS — how a domain name becomes a server's address
- Ports, sockets & basic routing
Real-World Industry Use Case
Every "this site can't be reached" error a user sees is a networking failure somewhere in this stack — DNS not resolving, a closed port, or a routing issue. Companies like Cloudflare and AWS build entire businesses on optimizing exactly these fundamentals at global scale.
How the Web Works
The specific case of networking that you'll touch daily as an engineer: what actually happens between typing a URL and seeing a rendered page.
- The HTTP/HTTPS request-response cycle
- What a browser does with the HTML/CSS/JS it receives
- REST APIs — how a frontend and backend actually communicate
- Status codes, headers & cookies
Real-World Industry Use Case
Debugging a blank page by opening browser DevTools and reading the Network tab is this entire module in action — every professional web developer does this multiple times a day. Understanding this is also the prerequisite for the Frontend and Backend modules later in this program.
Security & Privacy Basics
You don't need to be a security specialist to write safe code — but every engineer needs to understand the basic threats and why certain practices are non-negotiable.
- Encryption basics — what HTTPS is actually doing
- Common vulnerabilities: SQL injection, XSS, CSRF
- Why passwords are hashed, never stored in plain text
- The principle of least privilege
Real-World Industry Use Case
Almost every major data breach you've read about in the news traces back to one of these basics being skipped — an unhashed password database, an unvalidated input field. This is precisely why every serious company runs security/code reviews before shipping to production.
Ready to learn this — live?
See how this module fits into the complete curriculum.