HackerTube.dev

Steve Jobs rare footage conducting a presentation on 1980 (Insanely Great)

naji1234 · 2.8M views · 2011-12-12 · 23:00

Open on YouTube ↗

If playback is restricted in your region, try opening the original video. Use Mark watched to add it to your marked videos.

Overview

Rare footage of Steve Jobs giving a 22 minute presentation about Apple in 1980, donated to the Computer History Museum. In it he explains the company name and the bicycle-for-the-mind idea for computers.

On Hacker News

HN commenters cite it as proof that Jobs was a polished speaker from the start and quote its analogies about computers and people.

Recommended by 1 HN people across 1 months · HN mentions 2012–2026

Topics

Search by tags

What people said

mratzloff · 2014-01 · Strong recommendation

The thing that amazes me about Jobs is how he could present in such a way that it seemed so off-the-cuff and at the same time so polished. Anyone who has had to do presentations like these can learn a lot from watching him at work. In the NeXT video, for example, he's very good at tying everything together into a cohesive whole, and speaking to his audience in terms they'll understand. He uses practically no filler words ("uh", "um", "basically", etc.). Here's another presentation he did in 1980 that shows he had these skills almost from the very beginning: [VIDEO]

Read the original HN comment ↗
iancmceachern · 2026-05 · Reference

It reminds me of this Steve Jobs Clip: [VIDEO] He said, so many years ago, that there will become a time where computing power is so prevalent that we will stop using the person to make the computers job easier and start using the computer to make the humans job of interfacing with it easier. But in this context, it would mean the other side of increase productivity is decreased time to do the same work. These are the same thing.

Read the original HN comment ↗
samokhvalov · 2021-12 · Reference

This is great that you can do that. An experimental environment must be of the same size. Ideally, absolutely the same physically, to keep the same physical layout as on prod – bloat, etc – though, sometimes it's not allowed. Another problem here is that for each experiment, you might need a new environment. Plus, in larger teams, many people might want to do this work at the same time – so you end up combining efforts, synchronizing them, sharing environments. It slows you down. Or increases your cloud spending a lot. This is a kind of problem Steve Jobs described in his famous 1980 speech [1] about Apple: if we give each person their own computer, something special happens compared to the case when 10 persons share a single computer. Here it is the same: if we can give each engineer their own full-size DB copy for experiments, something special happens. They start moving much, much faster. SQL quality improves. DB changes (DDL, massive DML) stop failing. Finally, engineers start learning SQL, it's an eye-opener – they now can see how it works on large volumes (because they didn't have good environments for experiments before!) This is what we (Postgres.ai) have learned over the last couple of years developing Database Lab Engine [2]. It's an open-source tool for superfast cloning of Postgres databases of any size, based on copy-on-write provided by ZFS or LVM. On a single machine, you can have dozens of full-size clones up and running, conduct a lot of experiments at the sa

Read the original HN comment ↗

Sources

Video by naji1234, played through YouTube.

Data and selection notes

HN summaries and labels may contain AI errors. HN dates refer to discussions, not video publication.

HN Library: HackerTube export (2026-10-31) and open-index/hacker-news. Upstream summaries and classifications may contain AI errors.

Views, duration and playback status refresh separately from the published catalog. When an update fails, existing data remains visible.

Selection checks
  • SaaS & AI candidates: Topic keywords do not match
  • Editor-approved picks: Editorial review is required

Rule matches identify candidates. They do not guarantee video quality or financial results.

About the library and its sources