# Then vs now: building a computer

URL: https://ekom.blog/then-vs-now-building-a-computer/
Published: 2023-09-08
Author: Ekom
Topics: Tech, New & Old

> How building your own computer went from jumpers, ribbon cables and guesswork to tool-light assembly and compatibility checkers, and what is still worth knowing.

Building your own computer used to be a hobby for people who enjoyed reading manuals. Today it's closer to a grown-up Lego kit. The parts are the same in spirit, but almost everything about the experience got easier, and a few things got stranger.

Let's compare the two eras, then see whether building one is still worth it.

## What a PC is made of (it hasn't changed)

Whatever the decade, a desktop computer has the same ingredients:

- Processor (CPU), the brain.

- Motherboard, the circuit board everything plugs into.

- Memory (RAM), the short-term workspace.

- Storage, where files live.

- Graphics card, if you need strong graphics.

- Power supply, which turns wall power into the right voltages.

- Case and cooling, which hold it all and keep it from overheating.

Think of building a kitchen: the layout changed over the years, but you still need a cooker, a fridge and a sink.

## Then: patience, jumpers and a lot of cables

In the era of older PCs, building one involved a set of chores that sound alien now.

- Wide ribbon cables. Hard drives and optical drives connected through flat, grey ribbon cables (IDE), which were bulky and blocked airflow.

- Jumpers. Tiny plastic caps you moved on pins to set a drive as "master" or "slave", or to set a processor's speed. Get it wrong and nothing worked.

- Floppy drives for installing drivers, because drivers were not always downloadable.

- Bent pins. Many processors had pins on the chip itself, and one careless push could bend them.

- Manuals as the main help. If the board's booklet was unclear, you were on your own, or on an internet forum.

- Compatibility guesswork. Would this memory work with that board? You found out when you turned it on.

- Driver discs. Install the operating system, then hunt for a disc with graphics, sound and network drivers.

What it did well: it taught you how a computer works. Building one meant understanding it.

## Now: more standard, more checked

Modern building is more forgiving.

- Standard connectors. Drives use a thin SATA cable, or plug directly into the board (M.2 SSDs). No jumpers to set.

- Better guides. Most boards have clear diagrams, labelled headers and error lights. Video tutorials show every step.

- Compatibility checkers. Websites such as PCPartPicker let you pick parts and warn you when they won't work together.

- Tool-light assembly. Many cases and coolers are designed to need few tools.

- Software installs. Operating systems install from a USB stick, and drivers mostly arrive automatically.

- BIOS updates are easier. Many boards can update their firmware from a USB drive.

New parts also come with new things to learn: DDR5 memory arrived in 2021 and needs a board that supports it, new processor sockets, and graphics cards that are larger and hungrier for power than they used to be. Windows 11 also asks for certain security features on the machine. The manual's job hasn't gone away.

## What stayed the same

Some tips are as true now as ever:

- Static can damage parts. Touch bare metal on the case or wear a strap before handling components.

- Read the manual for the motherboard. It tells you exactly where each cable goes.

- Don't force anything. Parts click into place with moderate pressure.

- Add thermal paste correctly if your cooler doesn't come with it already applied. A small amount in the middle is enough.

- Build outside the case first if you want to test the basics.

- Check the power supply is big enough for your parts.

- Cable management matters. Tidy cables aid airflow, and a tidy PC is easier to fix later. Cable management for a tidy desk covers the principle.

## Is it still worth building one?

It depends on what you want.

Build your own if:

- You enjoy learning how things work.

- You want to choose each part, such as a quiet case or a particular graphics card.

- You plan to upgrade over time, swapping one part at a time.

- You can find the parts at a fair price where you live.

Buy ready-made if:

- You want a warranty on the whole machine and one place to call.

- Your time is more valuable than the saving.

- You're not near a reliable parts supplier. In some places, getting individual parts is hard, and repair shops are the safer route.

- You only need an ordinary machine for office work. A small desktop or laptop does the job for less hassle. For that kind of use, Mac mini and small desktops for a home office is worth a look.

Often, laptops have taken over from desktops for ordinary work. If you're choosing one, how to choose a laptop without getting lost in specs is a better start than a parts list.

## What building one teaches a web person

If you run a website, a custom PC is rarely something you need. But the lessons carry across:

- Know what each component does. When a site is slow, you ask the same questions: is it the processor, the memory, the storage or the connection?

- Check compatibility before you buy. Plugins, themes and servers have the same problem as memory and motherboards.

- Document your build. A note of what you installed and where is useful for a PC and for a website.

- Start with a plan. A budget and a purpose beat buying parts that look exciting.

## Key takeaways

- A PC is the same set of parts as ever, but connectors and tools became far simpler.

- Old builds meant jumpers, ribbon cables and bent pins; new builds mean checkers, M.2 and tutorials.

- Static, manuals, thermal paste and cable tidiness still apply.

- Build for learning and control; buy ready-made for convenience and warranty.

## Related reading

- Then vs now: building a website in 2010 vs 2023

- Then vs now: taking a holiday photo

- Then vs now: starting a website

If you were building a computer this weekend, what would it be for?

---

From Ekom (https://ekom.blog/). More: https://ekom.blog/llms.txt
