Abstraction, Layered Computing, and IT Fundamentals

Abstraction hides complexity by providing a simplified interface so we can use a system without needing to understand all its inner workings.
We don’t literally need to know the zeros and ones, but we rely on abstraction so we can operate complex systems without worrying about every detail.
Abstraction is used every day in the real world, often without us realizing it.

Car analogy: when you drive, you don’t operate the engine or transmission directly; you use a steering wheel, pedals, and a gear stick. Even if cars from different manufacturers have different internals, the basic interface remains familiar.
This is the essence of abstraction: hiding complexity by providing a common interface (steering wheel, pedals, gear stick, gauges).
The same principle applies to computers: we interact with a mouse and a keyboard, not with the hardware logic under the hood.
The course will use the under-the-hood metaphor to describe the area that contains the underlying implementation of a technology.

Abstraction helps us tackle very complex problems by breaking them into simpler ideas or tasks and stacking them in layers.
This layering concept is a fundamental principle that will be used throughout the course.
An everyday IT example of abstraction: error messages. For instance, a simple message like "file not found" conveys essential information and saves time debugging. Without such abstraction, troubleshooting would be much harder.
If a system did not abstract errors, we’d be left without guidance on where to start looking for solutions.
In prior material, it was noted that people don’t need to understand how a computer works to use it because abstraction makes things simpler. In IT, however, you do need to understand all the layers and how they interact to resolve issues.

Computers can be thought of as four main layers: hardware, operating system, software, and users. Understanding these layers helps us reason about how to fix problems and how different parts interact.
There are $4$ layers in this model. The layering approach makes it easier to understand, troubleshoot, and replace parts without rethinking the entire system.
Each layer provides a boundary that abstracts away details of the layer below it, enabling focus on the relevant interface.

Definition: the physical components of a computer; tangible objects you can hold.
Examples: laptops, phones, monitors, keyboards.
The hardware layer is the foundation; in this module you’ll learn all of the components and how they work, and you’ll even be able to build your own computer by the end of the module.

Definition: the software layer that allows hardware to communicate with the rest of the system and coordinates resources.
Purpose: enables hardware (often from different manufacturers) to be used with our system regardless of origin; acts as a common platform.
In upcoming lessons you’ll learn about the major operating systems in use today and the underlying components that make up an OS.
By the end of these lessons, you’ll have a solid grasp of the major components of any OS (e.g., Android, Windows) and be able to navigate any operating system.

Definition: the applications and programs that humans interact with directly.
Humans interact with software via apps, web browsers, word processors, and the OS itself.
Later in the course you’ll learn how software is installed and how to interact with different types of software.

Definition: the human element; often considered the most important layer in IT.
While IT work involves technical tasks, the user interface and user interactions drive most of the work (e.g., responding to user emails, fixing their computers).
By the end of the course you’ll learn how to apply your knowledge of how a computer works to fix real-world issues that can seem random or obscure.

We’ll approach issues by learning problem-solving tactics to identify issues and determine solutions.
There is a lot ahead, and this course will equip you with a structured approach to diagnosing and fixing problems.

The next instructor you’ll meet is Devin Tree Theron, a friend who will teach you about hardware and even show you how to build a computer from its components.
At Google, people come from diverse backgrounds (e.g., history degrees, economics degrees) and still succeed in IT by applying fundamentals and solving problems.
A common misconception is that you must follow a traditional path to succeed in IT. While many do follow traditional trajectories, the field often values practical ability to fix problems over formal background alone.
The benefit of IT is that what matters is your ability to fix problems and demonstrate strong fundamentals. People tend to come back once you prove you can solve issues.

Some people think they don’t need to learn low-level concepts (e.g., the TCP/IP model or the OSI model) and can focus solely on a single application or program.
There are situations where having foundational knowledge is integral to solving problems and supporting users effectively.
As long as you can work with users, solve problems, and provide good support, you’ll remain viable in IT.
Even in specialized areas, understanding the broader layers and their interactions helps you troubleshoot more effectively and communicate with others.
TCP/IP and OSI models are foundational frameworks for networking; familiarity with them can be crucial when solving network-related issues.

Abstraction simplifies usage and supports interoperability across diverse hardware and software ecosystems.
To be effective in IT, you should aim to understand how the four layers interact and how problems propagate across layers.
A strong emphasis on user interaction is essential; technology serves people, and user-focused problem solving is central to IT roles.
Be prepared to work with colleagues from varied backgrounds and to demonstrate your ability to fix problems, not just to know theory.