Hardware is the physical parts you could drop on your foot, and every single piece is doing one of four jobs.
Input devices turn something in the world into data: a keyboard, a mouse, a graphics tablet, a 3D scanner, a microphone, a soil moisture probe.
Output devices turn data back into something a person can see, hear or hold: a monitor, a speaker, a 3D printer, a laser cutter, a vibration motor.
Storage devices keep data when the power is off: a solid state drive, a hard disk, an SD card, a USB stick.
Processing devices do the actual work on the data: the CPU for general instructions, and a GPU for anything with a lot of pixels or polygons.
One gadget can hold two jobs at once, which is why a touchscreen counts as an input device and an output device stacked on top of each other.
Example
The vector drawing you make in Inkscape is data sitting in storage.
The laser cutter is an output device, turning that data into cuts through 3 mm acrylic.
The cutter's own control board is a processing device, reading the file one path at a time.
The limit switches that stop the head crashing into the frame are input devices.
CPU, RAM and Storage: Three Different Kinds of Fast
The CPU, or central processing unit, carries out instructions billions of times a second, and splits into cores that can each work on a different task.
RAM, random access memory, is the desk: fast to reach, small, and wiped the instant the power goes.
Storage is the filing cabinet: slow by comparison, hundreds of times bigger, and it keeps everything with the power off.
Open a 400 MB CAD assembly and the machine copies it from storage into RAM, then the CPU works on the RAM copy, not the file.
Run out of RAM and the computer starts shuffling parts of that model back to storage, which is why an 8 GB laptop crawls once the assembly gets big.
More cores speed up rendering and simulation, more RAM lets you keep more things open at once, so the two upgrades fix completely different complaints.
Tip
Open the task manager or activity monitor while you model and watch which figure pins at 100 per cent.
If it is memory, close browser tabs before you blame the software.
If it is the processor, drop the render quality or the mesh resolution instead.
The Operating System Is the Layer You Never Chose
The operating system manages the hardware for everything else on the machine: Windows, macOS, Linux, Android, iOS.
It hands out CPU time, remembers which file lives where and draws the windows, so the people writing apps do not have to solve those problems again.
Application software is what you open to do a job: Fusion 360, Tinkercad, Inkscape, Figma, a spreadsheet, a browser.
Utility software sits between the two doing housekeeping: file compression, backups, antivirus scans, formatting a drive.
A driver is a small piece of software that teaches the operating system how to speak to one particular device, such as your studio's specific 3D printer.
A file that opens on one machine and not another is nearly always an application problem, which is why file formats like .svg, .stl and .pdf matter more to you than the brand of computer.
Common Mistake
Saving only in one company's own format ties your whole project to one program and one login.
Export a neutral copy as .step, .stl, .svg or .pdf at every milestone.
A design folder that only opens in software your school stops paying for is a folder nobody can moderate.
Embedded Systems: Computers That Do Not Look Like Computers
Definition
Embedded system
A computer built into a larger product to do one fixed job, such as the chip that runs a washing machine cycle or a bike light.
Most of the computers you own are not laptops: they are in the washing machine, the microwave, the car key, the bike light and the traffic light on the corner.
Each of those has one fixed job, a tiny amount of memory, usually no proper screen, and software written into the chip at the factory.
A microcontroller such as an Arduino Uno or a Raspberry Pi Pico is an embedded computer you are allowed to program yourself, which is why so many design projects sit on one.
The Uno has 2 KB of RAM, about a millionth of what a mid range laptop carries, so sloppy code runs out of room fast.
Firmware is the software stored permanently on that chip, and updating it is deliberately harder than updating a phone app because a failed update can kill the whole product.
If your product must sense something and respond without a person watching, an embedded microcontroller beats a full computer on cost, size and power draw.
Case study
A classroom plant watering rig runs on a Raspberry Pi Pico with roughly 200 lines of code.
Its input is a capacitive soil moisture probe read once every ten minutes.
Its output is a 5V pump switched through a transistor for eight seconds.
The whole build runs from a phone charger and costs less than a textbook.
Open Source or Proprietary: Who Is Allowed to Change It
Proprietary software ships as a finished product: the source code stays with the company, and a licence agreement sets out what you may do with it.
Open source software publishes its source code under a licence that lets anyone read it, change it and pass the changed version on.
Blender, Inkscape, FreeCAD, KiCad and the Arduino development environment are all open source, and all of them are used professionally.
Open source is not the same as free of charge, and free of charge is not the same as open source: a browser based CAD tool can cost nothing and still keep its code locked.
Open tools suit school projects because they install at home with no licence key, so your work does not stop when the studio does.
Proprietary tools often win on polish, on support and on matching the file formats a manufacturer expects, which is a fair reason to choose them.
Choosing the Kit Before You Choose the Idea Is Backwards
Write down what the product must do first, then pick hardware and software that can conduct it.
Check the whole chain before you commit: a design is not makeable if the cutter wants .dxf and your drawing program only exports .ai.
Budget the dull parts too, because a missing SD card, power supply or USB cable will stop a build just as dead as a missing motor.
Exam technique
Record the software name and version you used, so the work is clearly traceable to you.
Write down machine settings that worked, such as 60 per cent power at 12 mm per second on 3 mm acrylic.
Keep dated exports in a backed up folder; a corrupted final file with no copy costs you evidence in Creating the solution.
Testing Whether Your Choice Was Right
Try one small test piece on the real machine before you cut the real thing, because that is cheaper than finding out on your final panel.
Ask whether a user without your account, your licence and your laptop could still run the product you made.
In Evaluating, judge the tools as part of the outcome: a good product made in software nobody else can open is only half a success.
Active recall
Sort these into the four hardware jobs: SD card, graphics tablet, GPU, 3D printer.
Why does more RAM fix a different problem from more CPU cores?
Give two things an operating system does that application software does not have to.
What makes an embedded system different from a laptop, beyond its size?
Explain why free of charge and open source are not the same thing.