Input, Output, and Connectivity

RAM and storage tell you where data can live. Input and output, almost always shortened to I/O, tell you how it moves between the computer and everything outside it.

Ask about direction, not the object

Pressing a key sends input in. Displaying the letter sends output back. Speaking into a microphone is input; music through speakers is output. So far this feels like sorting devices into two bins.

It is not, and a touchscreen is the clearest proof. Touch it and position data goes into the computer, so that is input. The same surface lights up to show you an image, so that is output. The same piece of glass, both directions, sometimes in the same instant.

Storage behaves the same way. Reading a file supplies input to a running program; writing one sends output to the drive. Nothing about the device settles it.

So the question to ask is never “what kind of device is this?” It is “which way is data moving in this particular action?”

Connections carry I/O

Every device needs a path for its data and control signals. USB, HDMI, audio jacks, network connections: cable, built-in socket, or radio.

The shape of a connector does not fix a direction. USB carries keyboard input, sends a document to a printer, reads from an external drive, and delivers power, all through the same kind of plug. A network connection sends and receives constantly.

Plugging something in is also only half of it. The computer needs a piece of software that knows how to talk to that particular device, which is why a brand-new printer or webcam sometimes does nothing at all until something is installed. Chapter 3 comes back to how that works.

I/O is often the slow part

The CPU works on a timescale that physical devices simply cannot match. A program can look completely busy while it is doing nothing but waiting: for a file, for a printer, for a server on the other side of the world. During that wait the processor may be almost idle.

This is why “the computer is slow” is the beginning of a diagnosis rather than the end of one. CPU-bound work, not enough RAM, a slow drive, and waiting on I/O all feel similar from the outside and need completely different responses. The four-job model is what lets you ask which one is actually happening.

Ask Monty about your own machine

You have a real computer in front of you with real behavior worth explaining. Pick something it does that has always puzzled you, and ask Monty:

My computer does [describe what happens]. Using input, processing, storage, and output, which part is most likely responsible, and what would I look at to check?

Monty is free through the rest of this chapter. Using it on a machine you actually own, rather than a textbook example, is where this model starts to feel like yours.

We have now named the parts and the paths between them. Next: the board they all plug into, and why the thing in the middle is not the thing in charge.