Open Course

Computing Fundamentals

Computing fundamentals covers the foundational concepts underlying all computer systems: binary representation, logic gates, processor operation, memory, storage, operating systems, and networking. It provides the mental model for understanding how software instructions become physical actions.

itComputer fundamentals | OpenSkills.info

Course pathWalk it in order

Look it upDip in anytime

Go furtherLeaves this page

Don't Panic -- Computing Fundamentals

Right then. You have in front of you a two-minute tour of how a computer actually works, written for people with better things to do. It is not a textbook and will not make you memorize a datasheet. It hands you a map of the machine so that the next time something misbehaves, you know which layer is lying to you.

The problem this set of pages solves: a computer is several quiet subsystems pretending to be one gadget. Before you got here, the usual introduction was either a wall of acronyms, CPU, DRAM, API, DNS, TCP, stacked until the eyes glaze, or a brochure that shows you pictures of keyboards. This course skips both.

Three ideas carry the whole thing.

First, the machine is layered. Hardware supplies resources, software supplies instructions, and the operating system, the software managing processors, memory, files, devices and the network, is the referee in the middle. Once you see that a program, stored instructions, is not a process, the running copy that holds state and consumes resources, a lot of confusing behavior starts to look like coordination instead of chaos.

Second, data has no innocent meaning. Bits are of themselves silent. A byte is just a run of zeroes and ones until a format or character encoding, the mapping from stored units to characters, gives it meaning. The same eight bits can be a number, a letter, a pixel or part of an instruction. Stare at a file long enough and it stays stubbornly meaningless until you say what it is.

Third, the machine is not uniform. Main memory, the RAM, forgets everything when the power goes, while storage does not. Underneath it all sits the page cache, a slice of main memory that holds file chunks, which is why a write may not reach the disk for a while and a read may not touch the disk at all. These gaps are where 'it should just work' goes to die.

The genuinely surprising thing: your tidy slogan 'I saved it, so it is safe' is backwards. Writing bytes is a request, not a receipt, and memory does not empty the instant power leaves, which has consequences for trust most people only discover far too late.

Start with the introductory page for the calm version of the map, then the slides and cheatsheet as your glossary. When you are ready for the gritty underside, the field notes carry the judgment the intro was too polite to mention, and the timeline covers how all of this got built in a few loud decades.

Where this skill leads

Relevant careers

See how this topic contributes to broader role-level skill maps.

Sources